Skip to main content
Glama
Sign In
Creatomate MCP Server

Creatomate MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get a template source

get_template
Read-onlyIdempotent

Read a v2 template's native RenderScript source. This read-only operation does not render or mutate the template.

Instructions

One current v2 template read including native RenderScript source. Does not render or mutate.

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": {
      "template_id": "<template_id>"
    },
    "name": "get_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoExact private project profile label; no inherited/global key fallback.
template_idYesExact project template/render/feed ID. No URL, slash, traversal or query string.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds useful context that the read returns the current (not historical) version and includes native RenderScript source, but stays silent on permissions, rate limits, or version fallback behavior.

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 short, front-loaded sentences with no filler. The scope and the payload content lead, and the negative constraint follows compactly.

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?

For a read-only tool with no output schema, the description discloses the expected return content (native RenderScript source, current version). It is largely complete, though it could note what an agent should expect if the template is absent.

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%, with both account and template_id fully documented including pattern and format constraints. The description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (read) and resource (current v2 template), and clarifies the payload includes native RenderScript source. The singular 'One' implicitly distinguishes it from list_templates, though no sibling is 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 Guidelines3/5

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

The clause 'Does not render or mutate' scopes the tool away from render and mutation operations, implying usage. However, it never states when to reach for this versus get_render or list_templates, leaving the selection context to inference.

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