Skip to main content
Glama

AMIRA — Africa Multiple Research Data

by io.github.AM-Digital-Research-Environment
OverviewDiscussionsAdmin

Search podcasts

search_podcasts
Read-onlyIdempotent

Search podcast metadata and transcripts. Text-only hits include snippets; full transcripts require get_podcast with opt-in.

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 20, max 100
offsetNo
personNoA speaker/host name; either name order works
seriesNoSeries title, partial (e.g. 'Cluster Conversations')
keywordNoEvery word must occur in the title, abstract or transcript; quote a phrase to match it exactly
year_toNoLatest year
languageNoName or ISO code — 'French', 'fr', 'fra' all match
year_fromNoEarliest year

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / keyword / description
      Previous value: -"Matches title, abstract — and the transcript"New value: +"Every word must occur in the title, abstract or transcript; quote a phrase to match it exactly"
    • addedInput schema / properties / keyword / maxLength
      Added value: +1000
    • addedInput schema / properties / language
      Added value: +{
+  "description": "Name or ISO code — 'French', 'fr', 'fra' all match",
+  "maxLength": 1000,
+  "type": "string"
+}
    • addedInput schema / properties / person / maxLength
      Added value: +1000
    • addedInput schema / properties / series / maxLength
      Added value: +1000
    • changedInput schema / properties / year_from / description
      Previous value: -"Earliest episode year"New value: +"Earliest year"
    • changedInput schema / properties / year_to / description
      Previous value: -"Latest episode year"New value: +"Latest year"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the safe read-only/idempotent/non-destructive profile. The description adds genuinely new behavior: text-only hits return snippets while full transcripts require a separate opt-in call to get_podcast. It omits pagination behavior despite limit/offset params.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly packed sentences with zero filler; the resource scope is front-loaded and the fallback-to-get_podcast caveat follows immediately.

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?

With no output schema, the description usefully characterizes the return shape (snippets vs full transcripts), which is the key thing an agent needs to know. Pagination and ranking semantics for the 8 optional filters are left implicit, a minor gap.

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 88%, so the schema itself documents nearly all parameters (keyword matching rules, language ISO codes, partial series titles). The description adds no parameter-level detail, which is acceptable at this coverage level.

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?

States a specific verb+resource ('Search podcast metadata and transcripts'), which cleanly separates it from siblings like search_videos and search_publications. It doesn't explicitly name a sibling it is not, but the resource scope is unambiguous.

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?

Explicitly routes the agent to get_podcast for full transcripts and notes the opt-in requirement, giving a clear when-to-use-this-vs-that condition. No when-not guidance, but the alternative is named with its selection condition.

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

All AMIRA — Africa Multiple Research Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources