Skip to main content
Glama

Meta-Stamp Pockets

by app.railway.up.metastampv3-production
OverviewDiscussions(1)Admin

search_pockets

Search the Meta-Stamp Pockets catalog by keyword, creator email, or content category. Use this tool when an AI agent needs to discover available licensed content before pulling it. Ideal for finding relevant pockets when the agent knows what topic or creator it needs but not the specific pocket ID. Does NOT retrieve content — use pull_content with the returned pocket_id to access actual content. Works without authentication for query, isrc and content_type; anonymous results omit content_url and creator_id, which are returned only with a valid Bearer token (pkt_ API key). The query parameter is matched as a literal keyword and accepts natural language search terms or category keywords; the creator_email parameter restricts results to a single creator by their email address and requires an API key (anonymous calls using it are refused with an api_key_required error and a registration_url). The isrc parameter is an exact full-ISRC lookup. Provide at least one of query, creator_email or isrc. Returns matching pockets with their IDs, titles, descriptions, creators, content types, and pricing tiers. Each row also carries catalog_id, access ('open' or 'closed') and delivery ('file' or 'listing'). Closed-catalog rows cannot be pulled and never include content_url; listing rows show title, isrc and owner and never include content_url. Unlisted pockets are excluded from results unless found by an exact isrc match. Use the limit parameter to control page size.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isrcNoOptional exact ISRC lookup: the full 12-character code, dashes allowed (e.g. 'USRC17607839' or 'US-RC1-76-07839'). Matches case- and dash-insensitively; a partial ISRC is rejected. This is the only search that also returns unlisted pockets.
limitNoMaximum number of results to return per page. Defaults to 10, maximum 50 for search results.
queryNoNatural language search terms or category keywords to find matching content pockets. Optional when creator_email or isrc is provided.
content_typeNoOptional filter to show only pockets in a specific content category or source type, such as 'youtube', 'webpage', 'video', 'text', 'image', or 'audio'.
creator_emailNoOptional filter to show only pockets created by the creator with this email address. Case-insensitive exact match on the email. Requires an API key; refused for anonymous callers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / creator_email / description
      Previous value: -"Optional filter to show only pockets created by the creator with this email address. Case-insensitive exact match on the email."New value: +"Optional filter to show only pockets created by the creator with this email address. Case-insensitive exact match on the email. Requires an API key; refused for anonymous callers."
    • addedInput schema / properties / isrc
      Added value: +{
+  "description": "Optional exact ISRC lookup: the full 12-character code, dashes allowed (e.g. 'USRC17607839' or 'US-RC1-76-07839'). Matches case- and dash-insensitively; a partial ISRC is rejected. This is the only search that also returns unlisted pockets.",
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Natural language search terms or category keywords to find matching content pockets. Optional when creator_email is provided."New value: +"Natural language search terms or category keywords to find matching content pockets. Optional when creator_email or isrc is provided."
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses anonymous vs. authenticated behavior (content_url and creator_id omitted anonymously), the api_key_required refusal for creator_email, the closed-catalog pull restriction, listing-row field limits, and the unlisted-pocket isrc exception. This is exactly the behavioral context an agent needs beyond structured fields.

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

Conciseness3/5

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

Purpose and the pull_content exclusion are front-loaded, but everything is delivered as one dense run-on paragraph with repeated schema facts (isrc exactness, creator_email API-key requirement) and return-field enumeration. It is informative yet not efficiently partitioned or scannable.

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

Completeness5/5

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

Though there is no output schema, the description fully describes the result shape (IDs, titles, creators, content types, pricing tiers, catalog_id, access, delivery, and which rows omit content_url) and the paging control. Nothing an agent needs to call or interpret the tool is missing.

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 100%, so baseline is 3, but the description adds real meaning: the at-least-one-of constraint (not expressible via the empty required list), the literal-keyword matching semantics of query, and the auth caveat on creator_email. Some overlap with the schema's own isrc/creator_email text is the only detractor.

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 the Pockets catalog) and names the search dimensions (keyword, creator email, category). It clearly separates itself from pull_content ('Does NOT retrieve content'), but never mentions the sibling list_pockets, so an agent can't fully disambiguate between discover-via-search and list-all without inspecting both schemas.

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?

Gives explicit when-to-use ('discover available licensed content before pulling it'; 'knows the topic or creator but not the pocket ID') and a hard when-not ('use pull_content with the returned pocket_id'). The only gap is that it doesn't contrast with the list_pockets sibling.

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

All Meta-Stamp Pockets 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