Skip to main content
Glama

Search media assets

search_media_assets
Read-onlyIdempotent

Search public, active Core-managed Media Assets eligible for this website and return safe delivery variants plus schema.org MediaObject JSON-LD. Private and management records are never returned, and neither are documents that the website's editorial mapping gates, nor any document while that mapping cannot be read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_media_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOptional kind of asset to return; every kind when omitted.
queryNoOptional asset title or description search phrase.
cursorNoOptional opaque cursor returned by the previous page.
page_sizeNoInteger value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description does add genuinely useful behavior beyond that: only public/active Core-managed assets are exposed, private and management records are suppressed, and the tool fails closed (returns nothing) when the site's editorial mapping is unreadable. It says nothing about result volume or pagination semantics, so it is solid but not rich.

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?

Two sentences, front-loaded with purpose and return shape, with the exclusion rules consolidated afterward. The final clause ('nor any document while that mapping cannot be read') is dense and slightly convoluted, but no sentence is filler.

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 four optional parameters, no required inputs, and no output schema, the description carries the return-value burden well by naming the delivery variants and MediaObject JSON-LD. Pagination via cursor is documented in the schema, so the only remaining gap is guidance on choosing this tool over its search siblings.

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 100%, with each parameter documented inline (kind enum, query phrase, opaque cursor, page_size bounds), so the baseline of 3 applies. The description adds no extra meaning about how kind or query interact, or what happens when both are supplied.

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 opens with a specific verb and resource ('Search public, active Core-managed Media Assets eligible for this website') and even names the return shape (delivery variants plus schema.org MediaObject JSON-LD). It stops short of distinguishing itself from sibling search tools such as search_documents or search_content, so an agent must infer the boundary from the word 'Media Assets' alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no named alternative for adjacent searches (documents, pages, content). The exclusions that are stated ('private and management records are never returned', gated documents) describe what the tool yields rather than when an agent should pick it over a sibling.

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