Skip to main content
Glama
pghdma

CallRail MCP

create_form_submission

Create form submissions in CallRail to backfill offline leads from non-tracked channels, enabling proper attribution and lead-status workflow integration.

Instructions

Manually create a form submission (e.g. backfill an offline lead).

Useful when you receive a lead through a non-CallRail-tracked channel (paper form, in-person, etc.) and want it visible in CallRail with proper attribution + lead-status workflow.

Args: company_id: 'COM...' id. Required. referrer / referring_url / landing_page_url: All three required (CallRail enforces "either session_id or all 3 of these"). Use the original web context if known, or "(direct)" / "https://offline" placeholders for in-person leads. form_url: URL of the form page if applicable. form_data: Dict of form-field values (e.g. {"name": "Kevin", "email": "k@x.com", "phone": "412-555-1234"}). customer_phone_number / name / email: Set on the submission directly (overrides form_data if both are set). note, tags, value, lead_status: Standard lead-management fields. account_id: Auto-resolves if omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYes
referrerYes
referring_urlYes
landing_page_urlYes
form_urlNo
form_dataNo
customer_phone_numberNo
customer_nameNo
customer_emailNo
noteNo
tagsNo
valueNo
lead_statusNo
account_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions 'lead-status workflow' but does not disclose side effects, idempotency, rate limits, or potential triggers. The focus is on parameter usage rather than runtime behavior.

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 front-loaded with purpose and use case, then organizes parameters under 'Args:' in a readable inline list. Every sentence earns its place with no redundancy, and the length is appropriate for 14 parameters.

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?

Given the tool's complexity and absence of annotations, the description covers parameter semantics thoroughly and mentions workflow integration. It lacks a contrast with update_form_submission (which modifies existing submissions) and does not explain output, but the presence of an output schema mitigates the latter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description compensates fully by documenting all 14 parameters with constraints, examples, and relationships (e.g., 'either session_id or all 3', placeholders for offline leads, overrides). This adds high value 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 clearly states 'Manually create a form submission' with a specific use case 'backfill an offline lead'. This verb+resource structure is precise and distinct from sibling tools like get_form_submission and update_form_submission.

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 (non-CallRail-tracked channels) and what benefit it provides (attribution + lead-status workflow). It does not explicitly mention when not to use, but the context is clear enough for an AI agent to decide.

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/pghdma/callrail-mcp'

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