Skip to main content
Glama
Sign In

X Ads MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

X Ads Data Query

query_data
Read-only

Query X Ads data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, account_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.

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": {
      "body": "<body>"
    },
    "name": "query_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds meaningful procedural behavior: this is the final workflow step and depends on query_contexts outputs before the body can be constructed. It does not contradict annotations and adds context beyond them, though it omits any rate-limit, auth, or response-shape notes (the latter partly covered by the output schema).

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

Conciseness4/5

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

The description is front-loaded with the tool's role and necessary prerequisites, and most sentences carry actionable information. There is slight redundancy in repeating the step-2 requirement after listing it, but overall it is appropriately sized for a workflow-gated query tool.

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?

For a tool with one dynamic body parameter and an output schema, the description provides the critical procedural context: complete two query_contexts lookups first, inspect action-specific body structure, then construct the query. It leaves some ambiguity about supported query types, but the output schema and query_contexts dependency cover the main gaps.

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

Parameters3/5

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

The only parameter is a free-form body object with 0% schema description coverage. The description adds real meaning by saying the exact body structure must be obtained from query_contexts/actions_details and followed exactly, but it does not enumerate body fields or provide examples.

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 states a specific verb and resource: query X Ads data, positioned as Step 3 (FINAL) of a workflow. It distinguishes itself indirectly from query_contexts by casting that tool as prerequisite lookup rather than the final data query, though it does not clarify what kinds of X Ads data can be queried.

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

Usage Guidelines4/5

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

It gives explicit prerequisite steps with exact request values ('accounts', 'actions_details') and emphasizes always calling step 2 before querying. It does not state when not to use this tool or compare directly against execute_action, so it falls short of fully exhaustive guidance.

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 toolsInspect
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.

Resources