Marcora

import_community_blueprint

Use this tool to import a blueprint from the Marcora community exchange into your team's library. Once imported, use it like any of your own blueprints to generate content. Workflow: 1) Use list_community_blueprints to browse and find a blueprint. 2) Copy the blueprint_exchange_id. 3) Call this tool to import it. 4) Use list_blueprints to confirm it appears in your library. 5) Use create_content with the returned uuid as blueprint_uuid to generate content.

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": {
      "blueprint_exchange_id": "<blueprint_exchange_id>"
    },
    "name": "import_community_blueprint"
  }
}

Input Schema

Name	Required	Description	Default
`blueprint_exchange_id`	Yes	UUID of the community blueprint to import. Get from list_community_blueprints (the blueprint_exchange_id field on each item).
`_frontend_realtime_key`	No	For frontend progress updates only. Do not use from MCP clients.

Output Schema

Name	Required	Description
`id`	No	Blueprint record ID
`name`	No	Blueprint name
`uuid`	No	Unique identifier - use as blueprint_uuid in create_content
`content`	No	Blueprint template content
`created_at`	No	Unix timestamp of import
`team_visibility`	No	Visibility within your team
`imported_exchange_id`	No	Reference to original community 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?

Annotations already declare that this is a non-read-only, non-idempotent, non-destructive operation. The description adds meaningful context beyond that: the imported blueprint becomes usable like an owned blueprint, and the returned uuid is intended for create_content. It does not explicitly warn about duplicate imports, despite idempotentHint=false, which is the main remaining gap.

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 description is front-loaded with the core purpose, followed by a clean numbered workflow. Every step is relevant, though the final confirmation and generation steps could be trimmed slightly without losing essential 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?

Given an output schema exists and the single required parameter is fully documented, the description supplies the remaining operational context: prerequisites, the source of the identifier, and the post-import workflow. Nothing needed to invoke the tool correctly appears to be 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 coverage is 100%, and the schema already documents blueprint_exchange_id with its source in list_community_blueprints. The description reinforces where to obtain the identifier but adds no syntax, format, or constraint detail beyond the 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 states a specific verb and resource: import a blueprint from the Marcora community exchange into the team's library. It clearly distinguishes this action from browsing with list_community_blueprints and from generating content with create_content.

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?

It provides an explicit five-step workflow: browse with list_community_blueprints, copy the blueprint_exchange_id, call this tool, confirm with list_blueprints, then use create_content with the returned uuid. This tells the agent exactly when and how to use the tool relative to alternatives.

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?