Skip to main content
Glama

Get Asset

sirv_get_asset
Read-onlyIdempotent

Retrieve a library asset by ID to get its URL and metadata for AI processing or updates; optionally include the asset's metadata template.

Instructions

Get one library asset by id: its URL, file name, type, size, alt text, tags, favourite flag and custom metadata fields. Set includeTemplate to add the metadata template that the asset uses (one more request).

Use it to get an asset's URL before an AI tool, or to read its metadata before sirv_update_asset. Find the id with sirv_list_assets.

Read-only.

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": {
      "id": "<id>"
    },
    "name": "sirv_get_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAsset id, from sirv_list_assets
orgIdNoWorkspace id from sirv_list_organizations. Default: the workspace you signed in to
includeTemplateNotrue: also return the metadata template the asset uses, with its fields. Costs one more request. Default: false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • changedInput schema / properties / id / description
      Previous value: -"Asset ID"New value: +"Asset id, from sirv_list_assets"
    • addedInput schema / properties / includeTemplate
      Added value: +{
      +  "default": false,
      +  "description": "true: also return the metadata template the asset uses, with its fields. Costs one more request. Default: false",
      +  "type": "boolean"
      +}
    • 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.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read-only' adds nothing. The description does add real behavioral context: includeTemplate triggers one additional request, and the call is credit-free. Return contents are also spelled out, which matters since there is no output schema.

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 core action and return payload, then usage, then constraints. Most sentences earn their place, though 'Read-only.' duplicates the annotations and 'Credits: free.' is boilerplate whose placement mid-paragraph is slightly awkward.

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 no output schema, the description correctly enumerates the returned fields, and the annotations cover the safety profile, so an agent has enough to call it. Minor gaps remain around error behavior for an unknown id and what the custom metadata fields contain.

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 baseline is 3, but the description goes beyond the schema by explaining the cost/behavioral consequence of includeTemplate (one more request to attach the template) and by restating where the id comes from. orgId is left entirely to the schema.

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?

States a specific verb and resource ('Get one library asset by id') and enumerates exactly what comes back: URL, file name, type, size, alt text, tags, favourite flag, custom metadata. This clearly separates it from sirv_list_assets (many assets) and sirv_update_asset (mutation).

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?

Gives concrete use cases ('get an asset's URL before an AI tool', 'read its metadata before sirv_update_asset') and routes id discovery to sirv_list_assets. It never states an explicit when-not or a case where another sibling should be preferred, so it stops short of full routing guidance.

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