AskEditor

Search stock media

search_media

[read] Search stock providers for engaging real assets and (optionally) add the best hit to the library. Use for B-roll, a reaction GIF, a Lottie animation or a photo the project does not have; place an added one with add_timeline_clip. Not for the project's own files (use list_media). Returns up to 12 candidates {url, previewUrl, kind, title}, and with addTop the added {id, name, url}. Only configured providers work; one that is not answers with the sources that are. Related: list_media, add_timeline_clip.

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": {
      "project_id": "<project_id>"
    },
    "name": "search_media"
  }
}

Input Schema

Name	Required	Description
`items`	No	Many querys at once, max 20, each with this tool's fields; fields beside it are defaults.
`query`	No	Search keywords, e.g. 'success checkmark', 'city skyline'.
`addTop`	No	true: download the top result into the library (not a lottie).
`source`	No	giphy GIFs, lottie animations, pexels photos, pexels-video footage.
`project_id`	Yes	The AskEditor project this acts on (from list_projects).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Discloses the return shape (up to 12 candidates with url/previewUrl/kind/title, plus `added` on addTop) and a real environmental constraint: unconfigured providers respond with the list of working sources. It also clarifies the side effect of addTop (downloads into the library, lottie excluded). Minor tension: the '[read]' tag sits alongside readOnlyHint=false, though the body itself explains the add-to-library mutation.

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?

Front-loaded with the verb and a usage summary, then exclusions, return shape, and related tools — each sentence carries information. The single dense block is slightly overpacked, but there is no filler.

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?

Given no output schema, the description supplies the return shape, the addTop side effect, provider availability behavior, and the follow-up tool needed to place results. An agent has everything required to call it correctly and use the output.

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 the 3 baseline applies, and the description does add meaning beyond it: addTop is explained as 'add the best hit to the library' with the non-obvious caveat that it does not apply to lottie results. It does not mention the batched `items` parameter, but the schema covers that adequately.

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

Purpose5/5

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

Opens with a specific verb+resource ('Search stock providers') plus scope ('engaging real assets', optional add to library), and explicitly names the sibling it is not (list_media) for the project's own files. An agent can identify the tool's job without opening the schema.

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

Usage Guidelines5/5

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

Gives concrete use cases (B-roll, reaction GIF, Lottie, missing photo), an explicit exclusion ('Not for the project's own files (use list_media)'), and the correct follow-up tool ('place an added one with add_timeline_clip'). Both the when and the when-not are stated with named alternatives.

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

All AskEditor tools Inspect

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

Need Help?