DataForSEO MCP by InsightfulPipe

DataForSEO Setup Helper

query_contexts

Read-only

Helper for planning InsightfulPipe DataForSEO data queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_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

A3.9/5.0

Behavior4/5

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

readOnlyHint=true is consistent with the purely retrieval-oriented description. Beyond annotations it discloses useful traits: that accounts already contains available_actions (avoiding a redundant call), and that actions_details returns exact request bodies, identifiers, fields, time ranges and notes — real workflow context the agent can't get from annotations.

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?

Front-loaded purpose sentence followed by clearly labelled, short step/optional lines — easy to scan and act on. The 'xxxxxx' placeholder arrays are slightly noisy but serve to demonstrate the expected argument shape.

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 5-parameter discovery tool with an output schema (so return shapes needn't be explained), the description is nearly complete: it covers the workflow order, each mode's payload, and the required-actions prerequisite. The single gap is the undocumented `platform` parameter.

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?

Schema description coverage is 0%, so the description carries the full burden, and it does document request enum values, the actions array (via illustrative placeholder), and brand_id + workspace_id for the brands call. However the `platform` parameter is never mentioned anywhere, leaving one of five parameters completely unexplained.

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 opens with a specific framing: a planning/setup helper for InsightfulPipe DataForSEO queries, and then enumerates exactly what each request mode returns (metadata, available_actions, request bodies, brand guidelines). It effectively distinguishes itself as the pre-query discovery step, though it never names siblings like query_data or execute_action to make the boundary explicit.

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?

Strong sequencing guidance: Step 1 accounts, Step 2 actions_details marked 'REQUIRED before querying', plus two explicitly labelled optional calls. What's missing is routing against alternatives by name — it says the call is required before 'querying' but doesn't say to use query_data/execute_action afterwards.

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

All DataForSEO 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.