Skip to main content
Glama

get_asset_details

Retrieve full metadata and compliance documentation for a specific PixelVault asset by its ID.

Instructions

Get full metadata and compliance documentation for a specific PixelVault asset by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_idYesThe asset ID returned by search_assets.

Implementation Reference

  • Handler function for get_asset_details. Fetches asset metadata from the API using asset_id and returns formatted details including title, platform, compliance, license, format, price, description, and tone.
    async function handleGetAssetDetails(args) {
      const { asset_id } = args;
      let asset;
      try {
        const data = await apiFetch(`/asset/${asset_id}`);
        asset = data.asset || data;
      } catch (err) {
        return { content: [{ type: 'text', text: `Error fetching asset ${asset_id}: ${err.message}` }], isError: true };
      }
      const text = [
        `PixelVault Asset Details`,
        `ID: ${asset.asset_id || asset.id}`,
        `Title: ${asset.title || 'Untitled'}`,
        `Platform: ${asset.source_platform || 'Unknown'}`,
        `Compliance: ${asset.compliance_status || 'Cleared'}`,
        `License: ${asset.license_type || asset.use_case || 'See listing'}`,
        `Format: ${asset.type || 'Video'} | Price: ${asset.price ? `$${asset.price}` : 'See site'}`,
        `Description: ${asset.description || 'N/A'}`,
        `Tone: ${asset.emotional_tone || 'N/A'}`,
        `Approve and license: ${SITE_URL}`,
      ].join('\n');
      return { content: [{ type: 'text', text }] };
    }
  • Schema definition for get_asset_details. Defines input as an object with a required 'asset_id' string property.
    name: 'get_asset_details',
    description: 'Get full metadata and compliance documentation for a specific PixelVault asset by ID.',
    inputSchema: {
      type: 'object',
      properties: {
        asset_id: { type: 'string', description: 'The asset ID returned by search_assets.' },
      },
      required: ['asset_id'],
    },
  • src/index.js:185-185 (registration)
    Registration of get_asset_details in the CallToolRequestSchema handler. Routes the 'get_asset_details' tool name to the handleGetAssetDetails function via a switch statement.
    case 'get_asset_details': return await handleGetAssetDetails(args);
  • Helper function apiFetch used by handleGetAssetDetails to call the PixelVault API.
    async function apiFetch(path, options = {}) {
      const res = await fetch(`${API_BASE}${path}`, {
        headers: { 'Content-Type': 'application/json', ...options.headers },
        ...options,
      });
      if (!res.ok) {
        const text = await res.text().catch(() => res.statusText);
        throw new Error(`PixelVault API error ${res.status}: ${text}`);
      }
      return res.json();
    }
Behavior2/5

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

No annotations provided. Description states it's a read operation but doesn't disclose potential costs, required permissions, error behavior, or rate limits. Lacks details beyond basic purpose.

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?

Single sentence, 13 words, no fluff. Efficient but slightly terse; could include more context without being verbose.

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?

No output schema, and description doesn't outline what 'full metadata and compliance documentation' includes. Agents need more behavioral guidance for a tool that presumably returns complex data.

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 provides a clear description for the sole parameter 'asset_id' (returned by search_assets). Tool description adds no extra meaning beyond 'by ID', so 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?

Clearly states 'Get full metadata and compliance documentation for a specific PixelVault asset by ID.' Distinguishes from siblings: search_assets returns lists, generate_usage_agreement creates documents.

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

Usage Guidelines2/5

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

No explicit when-to-use or alternatives. Implies use with an asset ID, but doesn't mention prerequisites (e.g., need to call search_assets first) or when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rsweeting1/pixelvault-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server