Marcora

finalize_blueprint_draft

*SYNCHRONOUS — takes 1-3 minutes. This is expected; do not retry or assume an error.*
Use this tool to finalize (publish) a previously created blueprint draft into a full, usable blueprint. This is the final step in the draft workflow:

1) create_blueprint_draft — generates an AI-assisted draft the user can review/edit in the app
2) User reviews the draft at the link_url
3) finalize_blueprint_draft — converts the reviewed draft into a real blueprint

After finalizing, use the returned blueprint_uuid with create_content (passing it as blueprint_uuid) to generate content from this blueprint.

If you don't need the review step, use create_blueprint instead to create a blueprint directly.

**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": {
      "draft_uuid": "<draft_uuid>"
    },
    "name": "finalize_blueprint_draft"
  }
}

Input Schema

Name	Required	Description
`name`	No	Optional name override. If not provided, uses the draft's existing title.
`draft_uuid`	Yes	The UUID of the blueprint draft to finalize (returned as 'uuid' from create_blueprint_draft).
`category_id`	No	Optional category ID override. If not provided, uses the draft's existing category. Get valid IDs from list_content_categories.

Output Schema

Name	Required	Description
`name`	Yes	Blueprint name.
`summary`	No	AI-generated summary of what this blueprint produces.
`category`	No	Content category this blueprint belongs to.
`link_url`	Yes	Direct URL to view/edit this blueprint in Marcora.
`created_at`	No	Unix timestamp of creation.
`blueprint_dna`	No	AI-generated analysis of the template structure, tone, and section descriptions.
`blueprint_uuid`	Yes	Unique identifier — use as blueprint_uuid in create_content.
`source_content`	No	The template content from the finalized draft.
`team_visibility`	No	Visibility within your team (e.g. team, private).
`reference_content`	No	AI-polished reference version of the template content.
`input_instructions`	No	AI-generated guidance for users on what context to provide when generating from this blueprint.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the mutation profile is known. The description adds genuinely non-obvious behavior beyond that: the call is synchronous and takes 1-3 minutes, and the agent should not retry or interpret the wait as failure. It does not cover failure cases such as finalizing an already-finalized draft or permission requirements, which keeps it below a 5.

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?

The critical warning about the synchronous 1-3 minute runtime is bolded and placed first, which is the right front-loading. The numbered workflow and link-fidelity note are useful but slightly verbose, and the closing links paragraph reads as reusable boilerplate rather than tool-specific guidance.

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?

An output schema exists, yet the description still highlights the one return value an agent must act on (blueprint_uuid for the create_content handoff). Combined with the timing warning, prerequisite chain, and fallback tool, nothing an agent needs to invoke this correctly is missing.

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%, so all three parameters (draft_uuid, name, category_id) are already documented in the schema, including override semantics and where to get valid category IDs. The description adds no parameter-level detail beyond referencing the returned blueprint_uuid, so the 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?

States a specific verb and resource ('finalize (publish) a previously created blueprint draft into a full, usable blueprint') and immediately situates it among siblings create_blueprint_draft and create_blueprint. An agent can distinguish the three tools without opening any 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 three-step workflow with prerequisites (a draft must exist and be reviewed at link_url), names the alternative path ('If you don't need the review step, use create_blueprint instead'), and states the next tool to call (create_content with the returned blueprint_uuid). When-to-use, when-not-to-use, and alternatives are all covered.

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?