Skip to main content
Glama

Get Sirv File Metadata

sirv_cdn_get_file_metadata
Read-onlyIdempotent

Read metadata for one Sirv CDN file—title, description, tags, product fields, size, and content type—to check current values before updating it.

Instructions

Read the metadata of one file in the Sirv account connected to the workspace: title, description, tags and product fields, with file details such as the size.

Use it to see the current values before sirv_cdn_update_file_metadata. Do not use it for Studio library assets: use sirv_get_asset. To find a file's path, use sirv_cdn_search_files.

Inputs: file_path, the file's full path, such as /products/hero.jpg, and orgId for another workspace's Sirv account.

Read-only. Returns file_path, file_info (such as size and content type) and metadata. A path that does not exist returns a not-found error.

Credits: free.

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": {
      "file_path": "<file_path>"
    },
    "name": "sirv_cdn_get_file_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoWorkspace id from sirv_list_organizations. Default: the workspace you signed in to
file_pathYesFull path of the file in Sirv, such as /products/hero.jpg

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • changedInput schema / properties / file_path / description
      Previous value: -"Full Sirv file path, such as /products/hero.jpg"New value: +"Full path of the file in Sirv, such as /products/hero.jpg"
    • changedInput schema / properties / orgId / description
      Previous value: -"Organization ID (uses default org if omitted)"New value: +"Workspace id from sirv_list_organizations. Default: the workspace you signed in to"
    • addedInput schema / properties / orgId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description still adds real context by naming the return shape (file_path, file_info, metadata) and the failure mode ('A path that does not exist returns a not-found error'), plus the cost signal ('Credits: free'). The 'Read-only' sentence is somewhat redundant with annotations, keeping it short of a 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?

Front-loaded with purpose, then usage, then inputs, then behavior and cost, in short scannable sentences. Slight redundancy: 'Read-only' duplicates the annotations and the return-value sentence partially repeats the field list from the first sentence.

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?

With no output schema, the description compensates by describing what is returned and the not-found error path, and it covers both parameters and the multi-workspace case. Nothing an agent needs in order to call this correctly and interpret the result is missing.

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%, so both parameters are already documented in the schema, including the same /products/hero.jpg example. The description's 'orgId for another workspace's Sirv account' restates what the schema says about workspace id and default. Baseline 3 is appropriate since the schema does the heavy lifting.

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 opening sentence gives a specific verb ('Read the metadata') plus a precise scope ('one file in the Sirv account connected to the workspace') and enumerates the fields returned. It is immediately distinguishable from sirv_cdn_update_file_metadata and sirv_get_asset, which are named explicitly.

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?

It states a concrete when-to-use ('see the current values before sirv_cdn_update_file_metadata'), an explicit exclusion ('Do not use it for Studio library assets: use sirv_get_asset'), and a prerequisite routing hint ('To find a file's path, use sirv_cdn_search_files'). This is the full when/when-not/alternatives pattern.

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