Skip to main content
Glama
Sign In

Panda Video

by com.pandavideo
OverviewDiscussionsAdmin

Confirm AI eBook PDF

panda_confirm_ai_ebook_pdf
Idempotent

Finish the PDF upload started with panda_get_ai_ebook_upload_url (kind=pdf): the PDF is checked (exists, not empty, up to 15 MB, valid PDF) and becomes the eBook of that language. With upload_success=false the uploaded file is discarded instead.

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": {
      "video_id": "<video_id>",
      "lang": "<lang>"
    },
    "name": "panda_confirm_ai_ebook_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
langYesSame lang used to get the upload URL
video_idYesVideo ID
upload_successNofalse = the PUT failed; discard the file

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the actual validation rules (exists, not empty, 15 MB cap, valid PDF) and the destructive-adjacent discard path. Annotations already cover idempotency and non-destructiveness, so the remaining gap is auth/credit implications and what happens on validation failure.

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?

A single tight sentence pair with the predecessor tool, validation list, and discard behavior all front-loaded; no filler or redundant restatement of the title.

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 3-parameter confirmation step with no output schema, the description covers the setup link, validation semantics, and the failure path. Only a brief note on what is returned on success would make it fully self-sufficient.

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 100% and already explains lang and upload_success, so most of the description's parameter content is restatement. It does reinforce that upload_success=false discards rather than reverts, but adds no new syntax or format detail.

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

Purpose5/5

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

States a specific verb (finish/confirm) tied to a named resource (PDF eBook upload), names the exact predecessor tool panda_get_ai_ebook_upload_url, and defines the resulting state ('becomes the eBook of that language'). An agent can distinguish it from the many sibling create/upload tools without opening the schema.

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 states the prerequisite (a PDF upload started via panda_get_ai_ebook_upload_url with kind=pdf) and gives the alternative branch: pass upload_success=false to discard when the PUT failed. Both the when and the when-not are covered.

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

All Panda Video 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