Skip to main content
Glama

Search content

search_content
Read-onlyIdempotent

Search the team's content that can be shown on a screen: files, designs, apps, split screens and playlists. Newest first. Returns the id, name and type of each item.

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_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly content of this type. Leave out for all types.
limitNoDefault 20.
queryNoPart of the name. Leave empty to list recent content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / type / description
      Added value: +"Only content of this type. Leave out for all types."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety needs no restating. The description adds genuine value beyond that by disclosing result ordering ('Newest first') and the returned fields (id, name, type), which an agent cannot infer from the annotations.

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?

Three short sentences, each carrying unique information: scope/types, ordering, and return shape. Nothing is redundant and the resource scope is front-loaded.

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 states the returned fields and sort order, and the scope sentence covers what is searchable. It stops short of noting result-count/pagination expectations (limit caps at 50), a minor remaining gap for a listing tool.

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 coverage is 100%, with each parameter's meaning and defaults documented inline, so the baseline is 3. The description adds only indirect hints ('shown on a screen' maps to the type enum, 'Newest first' relates to unset ordering) and gives no extra syntax or matching-behavior detail.

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?

Uses a specific verb ('Search') plus a clearly scoped resource, and enumerates the content types (files, designs, apps, split screens, playlists) so the agent knows this is content, not screens/scenes/devices. It never explicitly contrasts with look-alike siblings such as list_scenes or list_screens, so routing still requires inference.

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

Usage Guidelines3/5

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

The phrase 'content that can be shown on a screen' implies the use case (finding playable content), and the schema notes 'Leave empty to list recent content' cover the browse mode. However, the description itself names no alternatives and gives no when-not-to-use guidance versus search_help or list_scenes.

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