Skip to main content
Glama

Search and import

search_and_import

Queue an asynchronous import of community clips matching a concept query, with optional result limit and aspect ratio; requires a write token.

Instructions

Queue asynchronous import; requires write token.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_and_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
max_resultsNo
aspect_ratioNo

Output Schema

NameRequiredDescriptionDefault
statusYes
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the mutation and external-reach profile is covered. The description does add two facts beyond the annotations: the work is asynchronous (implying the caller must poll, presumably via get_job_status) and a write token is required. It stops short of saying what is returned (a job id) or what gets created.

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 short clauses, front-loaded with the action and followed by the prerequisite; there is no filler or repetition. The brevity is efficient even if it leaves substance out.

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

Completeness2/5

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

An output schema exists so return values need not be described, but for an async write tool with three undocumented parameters the description omits the essentials: what the search portion does, how the caller should follow up on the queued job, and how the optional parameters shape results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden for all three parameters, yet it explains none of them. The semantics of query (search terms?), max_results (cap of 50), and aspect_ratio are left entirely to the bare schema types, which is a clear gap for a low-coverage schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and effect ("Queue asynchronous import"), but the tool's name promises a search step and nothing in the description explains what is searched or how the required query drives the import. An agent can tell it does not read data like search_clips, but cannot tell how search results relate to the queued import.

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?

The only guidance is the prerequisite "requires write token", which is useful but not when-to-use guidance. There is no statement of when to prefer this over search_clips or download_clip, nor any exclusion for cases where a synchronous result is wanted.

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