X (Twitter) MCP by InsightfulPipe

X Setup Helper

query_contexts

Read-only

Helper for planning InsightfulPipe X queries and write actions.

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

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?

With only readOnlyHint=true in annotations, the description adds meaningful behavior: it is a planning helper, actions_details must be called before querying, accounts already embeds available_actions, and brands can pull guidelines. It does not disclose auth or rate-limit behavior, but it does not contradict the read-only annotation.

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 step-by-step structure is front-loaded and easy to follow, with each step tied to a request mode. There is minor redundancy in calling out available_actions as already included in accounts, and the placeholder 'xxxxxx' examples are not especially informative, but the description remains efficient.

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?

Given five parameters, no schema descriptions, and an output schema, the description is largely complete for the setup workflow and need not explain return values. The main gap is the unexplained platform parameter, plus only implicit routing against sibling tools.

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 must carry parameter meaning. It explains the request modes, the actions list, and brand_id/workspace_id for the brands mode, but it never explains the platform parameter, leaving one of the five inputs opaque.

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 that this is a setup/planning helper for InsightfulPipe X queries and write actions, and enumerates the request modes it supports. It is more than a restatement of the title, but it does not explicitly distinguish itself from siblings such as 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 Guidelines4/5

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

It gives explicit sequencing: call request='accounts' first, then request='actions_details' with actions, and notes that actions_details is REQUIRED before querying. Optional calls for available_actions and brands are also identified, though alternatives to this tool are only implied rather than named.

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

All X (Twitter) 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.