Skip to main content
Glama

Plunder & Riffle Meme Engine

Set the phone call page

set_call_page
DestructiveIdempotent

/call: the human's phone page. Their video plays inside a phone; when it ends, their button appears. Saves it and returns shareUrl (/call/). Empty video_url clears the page. Free.

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_url": "<video_url>"
    },
    "name": "set_call_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
bot_idNoOptional: which of the account's bots (default its own).
cta_urlNohttps link the button opens, or "before" to send viewers to make their own phone (credited to this account). Empty = that same "before" button.
cta_textNoButton words shown when the video ends, ≤40 chars.
video_urlYeshttps YouTube link (watch / shorts / youtu.be), direct .mp4/.webm/.mov, or an engine temp page (bot.plunderandriffle.com/m/<id>, *.here.now).
caller_nameNoName on the phone ("Incoming call · <name>"), ≤40 chars.

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?

Beyond the annotations, the description discloses the key destructive behavior (empty video_url clears the page), the return value (shareUrl at /call/<ref>), and that the operation is free. This is consistent with destructiveHint=true and idempotentHint=true. It does not say whether prior settings are lost when partially updating, which is the remaining behavioral gap.

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?

The definition is compact and front-loads the resource identity ('/call: the human's phone page') before the behavior and return value. The fragmentary style ('Free.', 'Saves it and returns shareUrl') is terse but each fragment carries distinct information; nothing is redundant.

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 5-parameter setter with no output schema, the description covers the important pieces: what the page is, the clearing behavior, and the return value. It stops short of explaining what happens to unmentioned fields on a partial update or who can view the resulting page, which would round out a mutation tool.

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 already 100%, so the baseline is 3, but the description adds meaning the schema lacks: an empty video_url clears the page rather than erroring, which is critical for correct invocation of a required field. The other parameters (cta_url, cta_text, caller_name, bot_id) are fully documented in the schema and are not repeated here.

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 a specific resource (/call phone page) and states the concrete outcome: it saves the configuration and returns a shareUrl (/call/<ref>). The narrative framing ('Their video plays inside a phone; when it ends, their button appears') clarifies what is being configured, so an agent knows exactly what this tool produces, though it does not contrast itself with any sibling.

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?

Usage is implied rather than stated: you call this to publish a human's phone page, and passing an empty video_url clears it. There is no explicit 'use this when…' guidance, no prerequisites, and no pointer to alternatives for building a page another way.

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