Skip to main content
Glama

Add a reel link

add_video_link

A public Instagram, TikTok or YouTube Shorts link to swap a character into. Returns a source (probing); poll get_upload until ready.

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": {
      "url": "<url>"
    },
    "name": "add_video_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag this as a non-read-only, non-idempotent, open-world call, so the safety profile is covered. The description adds genuinely new behavior: the call returns a source in a probing state and completion must be observed via get_upload, which tells the agent this is asynchronous and must be polled rather than treated as a finished result.

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?

Two short clauses, no filler, and the follow-up action is placed where the agent will read it. The opening fragment reads as an input description rather than an action statement, which is slightly awkward but costs no space.

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 single-parameter, no-output-schema tool this covers the essentials: acceptable input constraints, that the result is a probing source, and how to wait for readiness. It could have mentioned what the source is subsequently used for (e.g. start_swap) to close the loop, but nothing required for a correct call is missing.

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%, so the only structured information about `url` is that it is a URI capped at 2048 characters. The description compensates by narrowing that to public Instagram, TikTok or YouTube Shorts links, adding platform and visibility constraints the schema does not express.

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 names the concrete resource (a public Instagram, TikTok or YouTube Shorts link) and the effect (swap a character into it), which is specific enough for an agent to know what this tool accepts. It is a noun fragment rather than a verb-led statement of the action, and it does not distinguish itself from siblings like use_own_video or create_upload, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'public' qualifier implies that non-public content must go through a different path, and 'poll get_upload until ready' hands the agent the immediate next step in the workflow. However, it never explicitly says when to choose this tool over alternatives such as use_own_video or create_upload, so the selection guidance is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.