Marcora

create_blueprint_draft

Use this tool to create an AI-assisted blueprint DRAFT from a prompt. This creates a draft blueprint template you can review and edit within the Marcora app before saving as a full blueprint. If you already have the full content of the blueprint template you want to make, you should use the create_blueprint tool instead. Only use this tool if you wish to give a prompt to have the AI generate the blueprint template and receive a URL to edit further.

Uses Studio Credits (charged when the draft completes, at the model's cost: 1 credit = 5¢, rounded up). If the team is out of credits the call fails with an `insufficient_credits` error (code 402) and no draft is created.

Workflow: 1) Provide instructions describing the blueprint you want to create. 2) Provide a name for the draft. 3) Provide initial markdown content (or empty if you want the AI to generate from the instructions alone). 4) Optionally get category_id from list_content_categories. 5) Review the AI-generated result, then have the user visit the link_url to finalize the blueprint. The returned `uuid` is the draft's identifier — pass it as `draft_uuid` to finalize_blueprint_draft.

**Links:** present `link_url` to the user exactly as returned — copy it character for character. Never retype, shorten, or rebuild a link or the IDs inside it.

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": {
      "instructions": "<instructions>",
      "name": "<name>",
      "content": "<content>"
    },
    "name": "create_blueprint_draft"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Display name for the draft (visible in the user's app).
`content`	Yes	Initial markdown content the AI will iterate on. Can be empty to let the AI generate from instructions alone.
`category_id`	No	Optional content category id from list_content_categories.
`instructions`	Yes	Prompt describing the blueprint to create (e.g. "A weekly product update email with sections for new features, fixes, and a tip of the week").

Output Schema

Name	Required	Description
`id`	Yes	Record ID for the blueprint draft.
`uuid`	Yes	Unique identifier for this draft. Pass as draft_uuid to finalize_blueprint_draft.
`title`	Yes	Blueprint draft name.
`content`	Yes	AI-generated blueprint template content in markdown.
`link_url`	Yes	Direct URL to view/edit this blueprint draft in Marcora.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say it is a non-read-only, non-idempotent, non-destructive write; the description adds substantive behavior beyond that: Studio Credit billing at the model's cost with rounding, a named failure mode (`insufficient_credits`, code 402) with the guarantee that no draft is created, and an exact-character link-presentation rule.

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 purpose and the sibling exclusion, then a numbered workflow that is genuinely scannable. It is somewhat long and has a stray leading indentation plus bolded section labels, but every sentence carries usable information.

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?

For a billed, multi-step creation tool this covers cost, failure behavior, workflow order, and what to do with the returned uuid and link_url; with an output schema present, no further return-value detail is required.

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 baseline is 3; the description goes slightly beyond by sequencing the parameters in a workflow (instructions, then name, then content-or-empty) and by pointing at list_content_categories as the source for category_id. It mostly restates schema content, so it does not earn a 5.

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 ('create an AI-assisted blueprint DRAFT from a prompt') and immediately contrasts it with the sibling create_blueprint, so an agent can pick between them without opening either schema.

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?

Gives an explicit when-to-use rule ('only use this tool if you wish to give a prompt to have the AI generate the blueprint template') and an explicit when-not ('if you already have the full content ... use create_blueprint instead'), plus the downstream finalize_blueprint_draft step.

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

All Marcora tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?