Skip to main content
Spotlight MCP exposes 20 tools. Each tool calls the same backend as the REST API. Parameters use camelCase in MCP; REST paths use the standard URL structure documented in the API reference.

Context and discovery

Brands, runs, and results

Perception

Topics and prompts (write)

Tool details

get_brand_context

Required: brandId Returns:
  • Language and target market
  • Prompt quota (remainingSlots, limits)
  • Topic and prompt counts
  • Report schedule and nextEstimatedScheduledFetchAt
Call this before creating or deleting prompts so the agent respects plan limits.

get_run_results / get_brand_last_results

Required: runId or brandId Optional: includeAnswer (boolean, default false), page, limit (max 500) Set includeAnswer: true only when you need raw LLM response text — responses can be large.

add_perception_prompts

Required: brandId, prompts (array) Each prompt object: Requires custom perception prompts to be enabled on the brand’s plan.

batch_create_topics_and_prompts

Required: brandId, topics (array) Each topic may include an existing id or a new name, plus a prompts array. Every prompt must belong to a topic. Prompt limits are enforced. Write tools return nextScheduledRunAt and a scheduling note — new prompts run on the next scheduled report, not immediately.

Discovering tools programmatically

MCP clients can call tools/list (JSON-RPC) to retrieve the live tool catalog with JSON Schema input definitions. A GET request to the MCP endpoint returns server metadata: