Skip to main content
Glama
Sign In

Ads Libraries MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Ads Libraries Execute Action

execute_action
Destructive

Execute Ads Libraries actions (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

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

  2. request='actions_details' with actions=['xxxxxx'] - Get detailed body structure (replace xxxxxx with actions from available_actions)

Rely on info from steps 1-2 to construct the action 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": "execute_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the agent knows this is a mutating, externally-visible operation. The description adds the workflow dependency and the instruction to follow the schema exactly, but says nothing about what state is changed, whether it is reversible, or what failure modes look like — notable gaps for a destructive tool.

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?

Four short sentences, front-loaded with the one thing that matters most (this is the final step) followed by the ordered prerequisite list. No filler or redundant restatement of the tool name.

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?

Output schema exists, so return values need no explanation, and annotations carry the safety profile. The description covers the prerequisite chain that is the main ambiguity, though it leaves the body payload entirely deferred to another tool — acceptable for a workflow-gated action but still a residual gap.

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?

There is one parameter (body) defined as a free-form object with additionalProperties=true and 0% schema description coverage, so the schema conveys no structure. The description partially compensates by pointing to query_contexts request='actions_details' as the source of the body structure, but it never describes the body's shape itself — the agent still must make another call to learn it.

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?

States a specific verb (Execute) and resource (Ads Libraries actions), and identifies itself as Step 3 (FINAL) of a workflow, which separates it from the query_* siblings. The nature of 'actions' itself is undefined, but the workflow framing keeps it actionable.

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 enumerates the two prerequisite calls to query_contexts with the exact request values ('accounts', 'actions_details' plus actions=['xxxxxx']). It states the ordering constraint and that the prerequisites are REQUIRED, leaving nothing to inference.

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