Tool reference
All 21 tools available over MCP and the API
Reading your data
These 14 tools answer questions and change nothing. Every one of them is scoped to your workspace — a key cannot read another customer's project, and asking for one returns the same answer as asking for a project that does not exist.
| Tool | What it returns |
|---|---|
listProjects | List the projects in this workspace with their tracked brand, market and last measurement date |
getProject | Full settings and context for one project: brand, market, tracked engines, categories, and the description read from the client's own site |
getBrandMetrics | One metric for the tracked brand plus the competitors ahead of and behind it |
getEngineBreakdown | The same metric split by which assistant answered |
getBrandMetricsByPrompt | Per-prompt breakdown: which tracked questions the brand shows up in and which it never does |
getSourceBreakdown | How citations split across source categories and content types |
listCitedSources | Domains or individual pages the models cited when answering, with how often each was used and how often the tracked brand appeared in those same answers |
getSourcePromptImpact | Which tracked prompts pull from one source, and through which engines |
listPublishingOptions | Cited domains where the client can actually buy a publication through our partner, with the partner's cheapest listed price |
getSiteAudit | The latest GEO audit of the client's own website: twenty-two checks in four groups, each with a verdict, what it measured and what to do about it |
listPrompts | The questions being tracked for a project, with their intent and topic tags |
listTopics | Topics for a project - the subjects buyers research |
listBrands | Brands discovered in the answers, with how they are classified and which name variants were merged into them |
getCreditUsage | Credit balance and what has been consuming it, split by tracking versus agent work |
Doing work
These 7 change something, and each returns a plan before it acts. The last four leave Scorra entirely and need the matching app connected in Settings → Integrations.
| Tool | What it returns |
|---|---|
addPrompt | Start tracking a new question for a project |
removePrompt | Stop measuring a tracked question |
startAgentTask | Put the Scorra agent to work on something: an article, an outreach email, an analysis, a content plan |
sendSlackMessage | Send a message to a Slack channel in the client's workspace - a summary, a finished draft, an alert |
saveToGoogleDoc | Save a long piece of writing - an article, a content plan, a report - as a Google Doc the client's team can read and comment on |
draftEmail | Put an email the agent wrote into the client's Gmail as a DRAFT, ready for them to read, adjust and send themselves |
saveToNotion | Create a page in the client's Notion - research, a content plan, a list of findings - under a page they name |
Defaults
When a tool is called without a period, it answers for the last 30 days across all engines. Say the window explicitly when it matters — last 7 days, on Gemini — because a summary that silently changed its window looks like the brand moved.
Discovering this list from code
GET https://app.getscorra.com/api/v1/tools Authorization: Bearer <key>
Returns the same catalogue filtered to your key's scopes, with JSON Schema for every input. That endpoint, this page and the MCP server all read one registry, so they cannot disagree.