Skip to main content
Glama
Sign In

YouTube MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

YouTube Execute Action

execute_action
Destructive

Execute YouTube action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

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

  2. request='actions_details' with platform + report_names or actions - Get detailed body structure

Two platforms: • youtube-analytics: channel_basic, video_performance, demographics, traffic_sources, revenue • youtube-data: channel_info, video_details, playlists, comments

Body must include 'platform' and 'action'. Follow the schema from step 2 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

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false, so the agent knows this is an irreversible external write. The description adds the workflow gating but says nothing about consequences of a bad body, retry behavior, or error handling — notable for a destructive external call, though not a contradiction.

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-loads the workflow position, then the prerequisites, then the platform enumeration — good ordering for scanning. Bullets and caps on REQUIRED make it skimmable; a small amount of the phrasing could be tightened, but nothing is filler.

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 not be explained, and the multi-step discovery path covers the otherwise empty body schema. For a one-parameter pass-through executor this is close to complete; only failure/destructive-effect context is thin.

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?

Schema coverage is 0% and the single 'body' property is a free-form object with additionalProperties:true, so the description carries the full burden — and it does add real semantics: 'platform' and 'action' are required keys, and the valid platform values are enumerated. What it omits (the full body field set) it correctly redirects to the actions_details call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Execute YouTube action" is essentially the tool name restated; the concrete effect is entirely determined by the opaque body. It does add value by naming two platforms and their action families (channel_basic, video_details, comments, etc.), so an agent knows the domain, but it never says what execution actually produces.

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?

Explicitly marks this as Step 3 (FINAL) and mandates two prior query_contexts calls with the exact request values ('accounts', 'actions_details'). That is strong sequencing guidance. It stops short of saying when NOT to use it versus query_data, but the workflow positioning covers the main risk.

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

All YouTube 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