Fetch metadata for a GhanaWeb TV video by numeric ID: title, page and image URLs, published/updated times, and YouTube embed URL.
Get GhanaWeb TV video metadata. Returns metadata for one GhanaWeb TV video by its required numeric id: title, page URL, image URL, published and updated times, and the YouTube embed URL. The video file itself is not returned.
| 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?
With no annotations, the description carries the full behavioral burden. It does useful work by disclosing the exact returned fields and explicitly stating 'The video file itself is not returned', but it never confirms the operation is read-only or notes any access constraints, so it stops short of full disclosure.
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?
Three short sentences with the core purpose front-loaded, then return fields, then the key limitation. Every sentence contributes and there is no filler, though the field enumeration is slightly list-like.
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?
No output schema exists, so the description correctly enumerates the returned fields and the one thing that is not returned. For a single-id metadata getter this is essentially complete; only routing guidance against siblings is absent.
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 only one parameter, so the schema already documents `id`. The description restates that it must be a required numeric id but adds no format, range, or sourcing detail beyond what the schema provides — the expected baseline when the schema does the heavy lifting.
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 (Get) and resource (GhanaWeb TV video metadata) and scopes it to a single video via its required numeric id, which implicitly separates it from the list-style sibling ghanaweb_videos. It is clear and unambiguous, though it never names the sibling it should not be used in place of.
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?
There is no explicit when-to-use or when-not-to-use guidance. An agent gets no instruction such as 'use ghanaweb_videos to discover ids first' or 'use ghanaweb_video_sections for section listings', leaving the routing decision entirely to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.