Skip to main content
Glama
Sign In
creative-tagger-mcp

creative-tagger-mcp

by stephenlavender
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_analysis

Retrieve the complete 21-dimension classification for a saved ad creative analysis by providing its ID.

Instructions

Get the full analysis result for a single saved library item by ID. Use after list_library when you need the complete 21-dimension classification (list_library returns a summary; this returns the full JSON).

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": {
      "analysis_id": "<analysis_id>"
    },
    "name": "get_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
brand_nameNoExact workspace brand_name from list_workspaces
analysis_idYesID of the analysis to fetch

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.4/5.0
Behavior3/5

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

No annotations provided, so description carries the burden. It states that the tool returns 'full JSON' but does not disclose other behavioral traits such as read-only nature, required permissions, or rate limits. For a retrieval tool, the transparency is adequate but could be more comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no wasted words. The first sentence clearly states the action, and the second provides usage context. Front-loaded and efficient.

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?

No output schema, so description partly compensates by mentioning 'full JSON' and '21-dimension classification'. However, it does not detail the return structure or fields. For a simple retrieval tool, it is mostly complete but could include a brief note on output structure.

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%, baseline 3. The description adds meaning by specifying 'by ID' and 'saved library item', clarifying the role of analysis_id. It does not explicitly describe brand_name but the tool context implies it is optional. The description adds value beyond 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?

The description uses specific verb 'Get', resource 'full analysis result for a single saved library item by ID', and distinguishes from the sibling tool list_library by noting that list_library returns a summary and this returns the full 21-dimension classification JSON.

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?

Explicitly states when to use: 'Use after list_library when you need the complete 21-dimension classification'. This provides clear context and alternative.

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

Deploy Server

Other Tools