Skip to main content
Glama

Carry out a publishing plan

publish_plan_execute

Uploads the approved plan's clips as separate jobs so a single failure doesn't stop the rest; each upload is final and uses daily quota, so run only after the person agrees.

Instructions

Upload the clips in a plan, one job each, so one failure does not stop the rest. Only call this after the person has agreed to the plan. Uploads cannot be undone and each one spends their daily quota.

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": {
      "items": "<items>"
    },
    "name": "publish_plan_execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesThe plan's items, as publish_plan returned them

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does add real context: one job per clip so a single failure does not abort the rest, uploads are irreversible, and each upload consumes the daily quota. It omits what is returned (job identifiers, per-item results), which matters since no output schema exists and a job_status sibling exists.

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?

Three short sentences, each carrying distinct information, with the core action first and constraints after. Slightly terse on outcomes, but no wasted words or redundant restatement of the 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?

For a one-parameter mutation with no annotations and no output schema, it covers the critical risks: irreversibility, quota spend, consent gating, and partial-failure behavior. The remaining gap is what the call returns so the agent can chain to job_status.

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 coverage is 100% and the single 'items' parameter is already described there as coming from publish_plan. The description adds no field-level meaning (e.g., how publish_at or privacy are interpreted), so the baseline 3 applies.

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 and resource ('Upload the clips in a plan, one job each') plus the execution semantics of the plan. It indirectly separates itself from publish_plan via the prerequisite, but never explicitly contrasts itself with planning or scheduling siblings such as schedule_clips_execute.

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?

Gives an explicit gate: only call after the person has agreed to the plan, which clearly excludes pre-approval use. It does not name the alternative tools or say when to prefer scheduling over immediate publishing, so guidance stops short of full when/when-not coverage.

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