Skip to main content
Glama

Outil.io

Search stock media

search_stock_media
Read-only

Chercher des vidéos ou photos libres de droits sur Pexels (illustrations, plans d’ambiance). Renvoie url à passer à import_video_media_url ou à une scène image.

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

Input Schema

NameRequiredDescriptionDefault
kindNovideo
limitNo
queryYes
orientationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds real value by naming the external provider (Pexels), the rights-free licensing status, and the shape of the return (a url to reuse) — but says nothing about result volume, pagination, or rate limits.

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 tight sentences, front-loaded with the action and followed by the follow-up instruction; nothing is wasted. Switches language from the English title and schema, a minor inconsistency rather than a structural flaw.

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?

For a four-parameter search tool with no output schema and no per-parameter documentation anywhere, the description is too thin — an agent cannot tell what limit does, what orientation means for results, or what the result payload looks like beyond a url. The provider and routing note help but do not close the gap.

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% across four parameters, so the description must carry the burden and largely does not. Only an oblique hint at the kind parameter appears ('vidéos ou photos'); query syntax, the limit default/max of 15, and the orientation enum are never explained.

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 and resource: search royalty-free videos/photos on Pexels, with the parenthetical noting illustrations and b-roll. It does not differentiate from sibling look-alikes such as search_photos or search_slide_images, so it stops short of a 5.

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 second sentence gives a concrete downstream routing hint (pass the returned url to import_video_media_url or to an image scene), which is genuinely useful. However, there is no explicit guidance on when to choose this tool over the sibling photo/slide search tools.

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.