Picorn

Picorn Blueprint: create the editor file

picorn_blueprint_create_file

Turn a compiled blueprintId into a persistent, fully editable Picorn editor file (native text, shape and image layers through the editor importer), render every slide and return the editorUrl, render URLs and a contact sheet. With a Picorn access token the file lands in your account and can be linked to a campaign idea (campaignId + ideaId) and scheduled with picorn_posts_schedule.

Input Schema

Name	Required	Description
`tags`	No
`title`	No
`ideaId`	No
`caption`	No	Post caption stored on the file and used when scheduling.
`campaignId`	No
`allowErrors`	No	Create the file although the last compile still reports errors. Default false.
`blueprintId`	Yes
`workspaceProjectId`	No
`workspaceProjectKey`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

addedInput schema / properties / allowErrors

Added value: +{
+  "description": "Create the file although the last compile still reports errors. Default false.",
+  "type": "boolean"
+}

AddedOct 16, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds real behavioral context — that the file is persistent and editable, that it renders every slide, that an access token determines whether it lands in your account, and that it returns editorUrl/render URLs/contact sheet. It does not cover idempotency or duplicate-file behavior, but it goes well beyond the annotations.

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-loads the core transformation and its output, then adds the account/campaign/scheduling nuance in the second sentence. Dense but every clause carries information; the single long first sentence is the only mild readability cost.

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 mutation tool with no output schema, the description usefully enumerates the returned artifacts (editorUrl, render URLs, contact sheet) and the side effects on the account. The remaining gap is the undocumented workspace scoping parameters, which the description never explains.

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 only 22% across 9 parameters, so the description has to compensate and only partly does: it clarifies blueprintId, campaignId + ideaId, and (implicitly) caption. tags, title, workspaceProjectId, and workspaceProjectKey are undocumented in both schema and description, leaving real gaps, though allowErrors and caption do carry inline schema descriptions.

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 ('Turn a compiled blueprintId into a persistent, fully editable Picorn editor file') and immediately scopes it against the upstream compile step and the downstream editor artifact. An agent can distinguish this from picorn_blueprint_compile and picorn_editor_create_project without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Clearly implies the prerequisite (a compiled blueprintId) and names the downstream pairing with picorn_posts_schedule plus the campaignId + ideaId linkage context. It stops short of explicitly saying when *not* to use this versus editor_create_project or what to do if no compile exists yet.

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

All Picorn 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?