Instagram MCP by InsightfulPipe

Instagram Setup Helper

query_contexts

Read-only

Helper for planning InsightfulPipe Instagram 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=['table_a', 'table_b'] – REQUIRED before querying. Returns the exact request body, required identifiers, fields, 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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds real behavioral value by disclosing the mandatory two-step gating (actions_details must precede queries) and noting that available_actions is redundant with the accounts response. It does not describe rate limits or what a failed lookup returns, but the gating constraint is the key trait an agent needs.

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-numbered layout is well front-loaded and each line maps to a distinct mode. Minor redundancy in advertising 'available_actions' as a standalone call immediately after saying it is already in the accounts response, but the note is clarifying rather than wasteful.

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?

An output schema exists, so return values need no elaboration, yet the description still summarizes what each mode yields (identifiers, exact request body, brand guidelines). The only real hole is the undocumented 'platform' parameter and no note on what happens if actions_details is skipped.

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?

With 0% schema coverage, the description carries the full burden and mostly succeeds: it explains that 'request' selects a mode, that 'actions' takes table names for actions_details, and that brand_id + workspace_id pair together for 'brands'. The 'platform' parameter is never mentioned anywhere, leaving one of five parameters 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 is upfront that this is a setup/planning helper for InsightfulPipe Instagram queries and enumerates the four request modes with what each returns. It is specific about the resource and the discovery workflow, but it never names the siblings (execute_action, query_data, prompts_menu) that an agent would otherwise confuse it with.

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?

Explicitly sequences usage: Step 1 'accounts' first, Step 2 'actions_details' is called out as REQUIRED before querying, and the remaining modes are marked Optional with their conditions. This is as clear a when-to-use map as a discovery tool can offer.

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

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