Fetch GhanaWeb TV video metadata by numeric ID, returning public title data and the YouTube embed URL for building or verifying embeds.
Get GhanaWeb TV video metadata. Returns public GhanaWeb TV metadata and the page's YouTube embed URL. The media itself is not retrieved.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric GhanaWeb TV video ID |
Changes observed during successful MCP inspections.
v1.17.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden, and it does disclose meaningful behavior: the output is public metadata plus the page's YouTube embed URL, and explicitly that the media itself is not retrieved. That last point prevents a costly wrong expectation. It stops short of covering auth requirements, error behavior, or whether the ID must be numeric-only.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with zero waste. The primary purpose is front-loaded and the negative constraint ('media not retrieved') follows immediately in the most useful position.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter read lookup with no output schema, the description covers what the tool takes, what it returns (metadata + embed URL), and one important limitation. It is nearly complete; only sibling routing and ID-format expectations are missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and there is a single parameter, so the schema already documents 'id' as a numeric GhanaWeb TV video ID. The description adds no further semantics about ID format or origin, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: 'Get GhanaWeb TV video metadata' by ID, with useful scope detail (public metadata + YouTube embed URL, not the media). It does not differentiate itself from the sibling ghanaweb_videos (the list counterpart), leaving the agent to infer singular-vs-plural from the name alone.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied rather than stated: the required 'id' parameter makes it clear this is a by-ID lookup, but the description never says when to use this versus ghanaweb_videos or ghanaweb_video_sections, and lists no exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.