Skip to main content
Glama
Sign In

Ads Libraries MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Ads Libraries Setup Helper

query_contexts
Read-only

Helper for planning InsightfulPipe Ads Libraries queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, other source metadata, AND available_actions (all ad library actions you can use).

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

Optional: request='available_actions' – Standalone call to list all available 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

NameRequiredDescriptionDefault
actionsNo
requestYes
brand_idNo
platformNo
workspace_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With readOnlyHint=true already declaring a safe read operation, the description adds useful behavioral context: what each request returns, that available_actions is included in accounts, and that actions_details is required before querying. It does not mention rate limits or error behavior, but it meaningfully supplements the annotation.

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 numbered step structure is front-loaded and easy to scan, with the required sequence called out clearly. Every line earns its place by mapping a request mode to its purpose.

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 less description, and the workflow is mostly complete for a read-only setup helper. The main remaining gap is that platform is undocumented and the tool's relationship to sibling query/execute tools is only implied.

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 compensate. It explains request modes, actions usage, and brand_id/workspace_id for brands, but it omits the platform parameter entirely and gives only an example format for actions rather than full type semantics.

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 role: a helper for planning InsightfulPipe Ads Libraries queries, with named request modes that clarify what it retrieves. It does not explicitly distinguish itself from siblings like query_data or execute_action, but the setup/planning purpose is clear from the steps.

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 step order: use request='accounts' first, then request='actions_details' as REQUIRED before querying, with optional standalone calls documented. It does not name sibling-tool alternatives, but the internal workflow guidance is strong.

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

All Ads Libraries 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