Skip to main content
Glama

Add a posted video's link

add_video_link

When the member pastes the Instagram, TikTok or YouTube link of a video they posted, record it. Cuttr reads its public view count after 1, 7 and 30 days. Without video_id it attaches to their latest video that has no link yet.

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
video_idNo

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?

No annotations are supplied, so the description bears the full disclosure burden. It usefully reveals downstream behavior (public view counts are read at 1, 7 and 30 days) and the default attachment behavior when video_id is absent, but says nothing about validation of the URL, duplicate handling, required permissions, or what the tool returns.

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, front-loaded with the trigger and resource, then the fallback rule. The middle sentence about view-count tracking is contextual rather than invocation-critical, but it is short enough to earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter write tool with no annotations and no output schema, the description covers the trigger and the video_id fallback but leaves the response shape, error/validation behavior, and duplicate-link semantics unstated. Adequate to call correctly in the happy path, thin for anything else.

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 0%, so the description must compensate for two undocumented parameters. It does explain video_id's default semantics well, but 'url' is only implied by 'pastes the ... link' — no statement about accepted formats, whether extra query parameters are tolerated, or whether a non-video URL is rejected.

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 gives a specific verb and resource ('record' a 'video's link') and enumerates the supported platforms (Instagram, TikTok, YouTube), so an agent knows exactly what the tool stores. It stops short of explicitly contrasting itself with the sibling log_video, leaving the boundary to be inferred.

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?

The trigger condition is concrete: use it when the member pastes a link to a video they posted. The video_id clause also tells the agent what happens when the optional parameter is omitted, which is genuine usage guidance. No explicit when-not-to-use or named alternative is given.

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.

Resources