X Ads MCP by InsightfulPipe

X Ads Setup Helper

query_contexts

Read-only

Helper for planning InsightfulPipe X Ads data queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, account_id, other source metadata, AND available_actions (all tables you can query).

Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, time ranges, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request": "<request>"
    },
    "name": "query_contexts"
  }
}

Input Schema

Name	Required	Description	Default
`actions`	No
`request`	Yes
`brand_id`	No
`platform`	No
`workspace_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With readOnlyHint=true already covering safety, the description adds useful behavioral context: the tool retrieves workspace_id, brand_id, account_id, source metadata, available_actions, and detailed request bodies with required identifiers, fields, time ranges, and notes. It does not discuss error behavior or pagination, but the workflow and expected retrieval outputs are well disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the tool's role and then structured as explicit steps and optional calls. Every sentence supports the workflow, including the useful clarification that available_actions is already included in the accounts response.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a multi-step discovery tool with five parameters and 0% schema description coverage, so the description needs to explain the workflow and it does so thoroughly. An output schema exists, so return-value details need not be exhaustive, but the unexplained 'platform' parameter keeps it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden and mostly succeeds: it explains request values 'accounts', 'actions_details', 'available_actions', and 'brands', plus the role of actions, brand_id, and workspace_id. The 'platform' parameter is not explained, which is the main remaining gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is a helper for planning InsightfulPipe X Ads data queries and explains the discovery workflow via request types such as 'accounts' and 'actions_details'. It implies differentiation from querying tools by stating 'actions_details' is required before querying, though it does not explicitly name or contrast with siblings like query_data or execute_action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit step-by-step guidance: Step 1 call request='accounts', Step 2 call request='actions_details' with actions and notes this is REQUIRED before querying. It also labels 'available_actions' and 'brands' as optional with their specific conditions, leaving little ambiguity about when to call this tool and with which request values.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All X Ads MCP by InsightfulPipe tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.