Skip to main content
Glama

acp_create_session

Create a checkout session to generate DOCX or PDF documents from templates. Pass template details and data records, then receive a Stripe checkout URL for payment.

Instructions

Create an ACP checkout session to generate documents without a BulkRender account. Pricing: $0.10/credit — DOCX = 1 credit, PDF = 2 credits. Minimum charge $1.00 (covers up to 10 DOCX or 5 PDF docs). Pass 'records' array (up to 200 objects) with one data object per document. Agents are responsible for passing all required template variable mappings — variables not provided will render as empty strings. Returns session_id, amount_due (USD), checkout_url (Stripe hosted payment page), and expires_at. Share checkout_url for browser payment, then poll acp_get_session until status is 'completed'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bearerTokenYesAny non-empty string — acts as your session bearer token
templateTypeYes'B' = use a public template by ID, 'C' = bring your own DOCX
templateIdNoRequired for template_type B — UUID from acp_list_public_templates
templateBufferNoRequired for template_type C — base64-encoded DOCX content
templateNameNoRequired for template_type C — filename e.g. my-doc.docx
recordsYesArray of data objects, one per document (max 200). Each object fills one document using the template variables. All documents use the same template and output_format. Keys must match the template field_schema variables — missing keys render as empty strings.
agentEmailYesEmail address to associate with this session
outputFormatNoOutput format for ALL documents in this session — docx (1 credit/$0.10) or pdf (2 credits/$0.20). $1.00 minimum applies.docx
Behavior4/5

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

With no annotations, the description covers critical behavioral details: pricing, credit consumption, minimum charge, maximum records, variable handling, return fields, and the need to poll acp_get_session. It does not mention potential side effects like credit reservation, but overall transparency is strong.

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?

The description is concise and well-structured, presenting pricing, usage flow, agent responsibilities, and return values in two clear paragraphs. Every sentence adds value without redundancy.

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 the absence of output schema and annotations, the description comprehensively covers input requirements, conditional logic, pricing model, return fields, and post-creation polling. It fully equips an agent to invoke this tool correctly.

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%, so baseline is 3. The description adds little to parameter semantics beyond what the schema already provides (e.g., conditional requirements for templateId/templateBuffer are already described in schema). No new parameter-level insights are offered.

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 clearly states 'Create an ACP checkout session to generate documents without a BulkRender account.' It outlines the tool's primary function, pricing, and return values, distinguishing it from siblings like acp_get_session or generate_batch.

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?

The description explains when to use this tool (for generating documents without an account) and provides pricing details. However, it does not explicitly contrast with sibling document generation tools (e.g., generate_batch, generate_document), leaving some ambiguity about optimal use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ayo-nci/bulkrender-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server