Skip to main content
Glama

Search catalog listings

search_assets
Read-only

Search the public catalog and return listing rows as Graunt's API gives them (GET /v1/listings), paginated. To find data for a person, use search, then fetch. search_match.words says how the listings matched the query: ALL (every word, or a synonym of it), SOME (some of the words), WORD_START (words that start with the query's words), SIMILAR_TITLE (titles spelled like the query) or NONE (no listing). On SOME and WORD_START each listing names its matched_words. When no listing matches, next_steps.post_request_url opens a buyer request with the query filled in.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch query string.
kindNoOnly listings of this kind of data, read from their media kind or their files.
limitNoMax rows; default 20, cap 100.
camera_viewNoOnly video listings shot from this camera view.
ai_generationNoKeep only packets whose seller declares this AI-generation extent: NONE (not AI-generated), PARTIAL or FULL. A seller declaration, not a Graunt finding. AI processing of real material (cleaning, labeling, transcribing, captioning, structuring) is not AI generation, and a packet that contains video declares NONE.
video_subjectNoOnly video listings whose footage shows this subject.
rights_public_useNoThe "Show it publicly" permission: NONE keeps only packets that grant no public use, including those that record no answer; EDITORIAL, PROMOTIONAL and COMMERCIAL keep only packets that grant exactly that use. The rights the seller declared on the listing, which Graunt records: a seller declaration, not a Graunt finding.
seller_credentialNoKeep only packets whose seller declares a credential: declared keeps listings whose seller declares at least one credential (a trade license, certification, business registration, membership or qualification); checked keeps those whose seller holds at least one that a Graunt operator checked against a registry. A seller declaration that Graunt records, never a Graunt finding, a score or a ranking input.
rights_license_familyNoKeep only packets whose seller names this license family. In order, the values stand for: Proprietary, CC0 (public domain), CC BY, CC BY-SA, CC BY-NC, CC BY-ND, CC BY-NC-SA, CC BY-NC-ND, MIT, Apache 2.0, BSD 2-clause, BSD 3-clause, GPL 3.0, LGPL 3.0, MPL 2.0, ODC-BY, ODbL, Public domain, U.S. Government work. The rights the seller declared on the listing, which Graunt records: a seller declaration, not a Graunt finding.
rights_training_allowedNotrue keeps only packets whose seller declares that AI models may be trained on them; false keeps only those whose seller declares they may not. The rights the seller declared on the listing, which Graunt records: a seller declaration, not a Graunt finding.
rights_sublicense_one_clientNoThe "Sublicensing to one client" permission: true keeps only packets a buyer may license for one client and pass the license through to that client; false keeps only those a buyer may not, including those that record no answer. The rights the seller declared on the listing, which Graunt records: a seller declaration, not a Graunt finding.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Only listings of this kind. video: video listings."New value: +"Only listings of this kind of data, read from their media kind or their files."
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "video"
      -]New value: +[
      +  "video",
      +  "audio",
      +  "images",
      +  "documents",
      +  "spreadsheets",
      +  "code"
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / rights_public_use
      Added value: +{
      +  "description": "The \"Show it publicly\" permission: NONE keeps only packets that grant no public use, including those that record no answer; EDITORIAL, PROMOTIONAL and COMMERCIAL keep only packets that grant exactly that use. The rights the seller declared on the listing, which Graunt records: a seller declaration, not a Graunt finding.",
      +  "enum": [
      +    "NONE",
      +    "EDITORIAL",
      +    "PROMOTIONAL",
      +    "COMMERCIAL"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / rights_sublicense_one_client
      Added value: +{
      +  "description": "The \"Sublicensing to one client\" permission: true keeps only packets a buyer may license for one client and pass the license through to that client; false keeps only those a buyer may not, including those that record no answer. The rights the seller declared on the listing, which Graunt records: a seller declaration, not a Graunt finding.",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / seller_credential
      Added value: +{
      +  "description": "Keep only packets whose seller declares a credential: declared keeps listings whose seller declares at least one credential (a trade license, certification, business registration, membership or qualification); checked keeps those whose seller holds at least one that a Graunt operator checked against a registry. A seller declaration that Graunt records, never a Graunt finding, a score or a ranking input.",
      +  "enum": [
      +    "declared",
      +    "checked"
      +  ],
      +  "type": "string"
      +}
  4. Changed2 schema fields changed
    • addedInput schema / properties / rights_license_family
      Added value: +{
      +  "description": "Keep only packets whose seller names this license family. In order, the values stand for: Proprietary, CC0 (public domain), CC BY, CC BY-SA, CC BY-NC, CC BY-ND, CC BY-NC-SA, CC BY-NC-ND, MIT, Apache 2.0, BSD 2-clause, BSD 3-clause, GPL 3.0, LGPL 3.0, MPL 2.0, ODC-BY, ODbL, Public domain, U.S. Government work. The rights the seller declared on the listing, which Graunt records: a seller declaration, not a Graunt finding.",
      +  "enum": [
      +    "PROPRIETARY",
      +    "CC0",
      +    "CC_BY",
      +    "CC_BY_SA",
      +    "CC_BY_NC",
      +    "CC_BY_ND",
      +    "CC_BY_NC_SA",
      +    "CC_BY_NC_ND",
      +    "MIT",
      +    "APACHE_2_0",
      +    "BSD_2_CLAUSE",
      +    "BSD_3_CLAUSE",
      +    "GPL_3_0",
      +    "LGPL_3_0",
      +    "MPL_2_0",
      +    "ODC_BY",
      +    "ODC_ODBL",
      +    "PUBLIC_DOMAIN",
      +    "GOVERNMENT_WORK"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / rights_training_allowed
      Added value: +{
      +  "description": "true keeps only packets whose seller declares that AI models may be trained on them; false keeps only those whose seller declares they may not. The rights the seller declared on the listing, which Graunt records: a seller declaration, not a Graunt finding.",
      +  "type": "boolean"
      +}
  5. Changed1 schema field changed
    • changedInput schema / properties / ai_generation / description
      Previous value: -"Keep only packets whose seller declares this AI-generation extent: NONE (not AI-generated), PARTIAL or FULL. A seller declaration, not a Graunt finding."New value: +"Keep only packets whose seller declares this AI-generation extent: NONE (not AI-generated), PARTIAL or FULL. A seller declaration, not a Graunt finding. AI processing of real material (cleaning, labeling, transcribing, captioning, structuring) is not AI generation, and a packet that contains video declares NONE."
  6. Changed4 schema fields changed
    • addedInput schema / properties / ai_generation
      Added value: +{
      +  "description": "Keep only packets whose seller declares this AI-generation extent: NONE (not AI-generated), PARTIAL or FULL. A seller declaration, not a Graunt finding.",
      +  "enum": [
      +    "NONE",
      +    "PARTIAL",
      +    "FULL"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / camera_view
      Added value: +{
      +  "description": "Only video listings shot from this camera view.",
      +  "enum": [
      +    "FIRST_PERSON",
      +    "AERIAL_OR_DRONE",
      +    "VEHICLE_OR_DASHCAM",
      +    "FIXED_CAMERA",
      +    "OTHER"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / kind
      Added value: +{
      +  "description": "Only listings of this kind. video: video listings.",
      +  "enum": [
      +    "video"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / video_subject
      Added value: +{
      +  "description": "Only video listings whose footage shows this subject.",
      +  "enum": [
      +    "PEOPLE_TALKING",
      +    "PEOPLE_IN_ACTION",
      +    "PEOPLE_HANDLING_OBJECTS",
      +    "HOW_TO_AND_TASKS",
      +    "SPORTS_AND_FITNESS",
      +    "MUSIC_AND_PERFORMANCE",
      +    "ANIMALS",
      +    "NATURE",
      +    "CITIES_AND_BUILDINGS",
      +    "DRIVING_AND_TRANSPORTATION",
      +    "INDUSTRY_AND_WORK_SITES",
      +    "FOOD_AND_COOKING",
      +    "PRODUCTS_AND_RETAIL",
      +    "ANIMATION",
      +    "VIDEO_GAMES"
      +  ],
      +  "type": "string"
      +}
  7. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, but the description adds real behavior: results are paginated rows as the API returns them, 'search_match.words' classifies match quality (ALL/SOME/WORD_START/SIMILAR_TITLE/NONE), and 'matched_words' only appears for SOME and WORD_START. It stops short of auth, rate-limit, or result-size behavior, so a 4 rather than 5.

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?

It is a single dense paragraph that front-loads purpose and then explains return semantics and fallback, with no filler sentences. It is slightly packed and mixes response-field guidance into one block, but every sentence carries information.

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 11 optional parameters, no required fields and no output schema, the description usefully explains the pieces of the response an agent must interpret (match classification, matched_words, next_steps). It leaves the full row shape to the API, which is acceptable given the endpoint reference, but richer return guidance would push it higher.

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% and the enum values (kinds, camera views, rights modes, license families) are fully documented in the schema itself. The description adds nothing parameter-specific, so the baseline 3 applies.

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?

The first sentence names a specific verb and resource ('Search the public catalog'), states the return shape ('listing rows') and the underlying endpoint (GET /v1/listings) plus pagination. It also distinguishes itself from the person-oriented route by pointing to 'search, then fetch', so an agent can tell what this tool is for 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 Guidelines4/5

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

It explicitly routes person-data lookups to 'search, then fetch' and offers a fallback path ('next_steps.post_request_url') when nothing matches, which is actionable when-to-use context. It does not say when to prefer this over other catalog siblings such as get_asset or match_video_spec, so there is a modest gap.

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