Orchestor MCP

MCP Tools

The hosted core profile contains the following tools. A connection’s available tools and exact input schemas come from tools/list; inspect them before calling a tool.

Tool catalog

ToolOperationPurpose
brands_listReadList brands
brands_getReadRead a brand
topics_listReadList topics
topics_getReadRead a topic
prompts_listReadList prompts
prompts_getReadRead a prompt
answers_listReadList answers
answers_getReadRead an answer
get_visibility_reportReadRetrieve visibility reports
get_citations_reportReadRetrieve citation reports
get_sentiment_reportReadRetrieve sentiment reports
get_query_fanouts_reportReadRetrieve query fanout reports
get_web_search_results_reportReadRetrieve web search result reports
search_toolsReadSearch additional read-only tools
get_tool_schemaReadRead a discovered tool schema
execute_toolReadExecute a discovered read-only tool
prompts_createPreviewPreview prompt creation
create_issueWriteCreate an issue

Discover workspace data

Start with brands_list, then use topics_list or prompts_list. List responses provide IDs to pass to the corresponding detail tools. topics_list accepts an optional brand_id; prompts_list accepts an optional topic_id.

{ "limit": 20 }

Example input for brands_list. Hosted OAuth determines the workspace.

When a response includes a next cursor, pass it to the next request instead of treating the first page as the complete result.

Retrieve reports

Use get_visibility_report for mentions and visibility, get_citations_report for cited sources, and get_sentiment_report for sentiment. Their schemas define supported metrics, dimensions, filters, and date ranges.

Retrieve visibility and citation reports for the same period. Explain the difference between brand mentions and citations, and identify the source data for each conclusion.

Find additional read-only tools

  1. Use search_tools to search by purpose.
  2. Use get_tool_schema to inspect the selected tool’s inputs.
  3. Use execute_tool with the discovered name and valid arguments.

This discovery path is read-only. It does not discover or execute write tools. Available additional tools depend on the connection profile.

Preview and write operations

In the hosted preview surface, prompts_create validates and previews prompt creation. A persisted creation requires write authorization and a tool surface that permits it. create_issue creates a workspace Issue and requires write permissions.

Check the tool’s required fields and annotations, confirm the target workspace and changes, and do not treat a preview as a persisted resource.