OrgLines

Create lead

create_lead

Create a CRM lead in the caller's active workspace. Use for capturing an enquiry from any channel (e.g. a Facebook lead). The lead is filed under the caller's active tenant and attributed to them. Pass 'source' to record the channel it came from. CONFIRMATION: this tool is PROPOSED, never performed directly. You get status='confirmation_required' with an action_id and a plan_token, and the write happens only after confirm_action.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_lead"
  }
}

Input Schema

Name	Required	Description
`tags`	No
`email`	No
`phone`	No
`title`	No
`budget`	No
`custom`	No	The workspace's own fields (keys from crm_list_fields): {key: value} sets, {key: null} removes, other keys stay. Values are validated by type — an enum lists its allowed options, money_eur accepts EUR only.
`source`	No
`company`	No
`message`	No
`lastName`	No
`firstName`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the full confirmation protocol: the call is only PROPOSED, returns status='confirmation_required' with action_id and plan_token, and the write occurs only after confirm_action. It also explains tenant scoping and attribution to the caller, which annotations cannot convey.

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 purpose, then usage, then a clearly labeled CONFIRMATION block. Sentences are tight and every one adds information; only the attribution sentence slightly overlaps with purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter write tool with no output schema, the confirmation flow is explained well, but the description is thin on field-level semantics and does not say what a successful lead object contains or how validation failures surface. Adequate but with clear gaps.

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

Parameters2/5

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

Schema description coverage is only 9% across 11 parameters, so the description must carry most of the burden but only explains 'source' (the channel). The nine other fields, including the nested 'custom' object and the zero-required-parameter behavior, get no guidance in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a CRM lead in the caller's active workspace') plus the intent ('capturing an enquiry from any channel'). It is clearly a lead-creation tool distinct from siblings like update_lead or create_lead_source, though it never names an alternative explicitly.

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?

Gives clear when-to-use context ('capturing an enquiry from any channel, e.g. a Facebook lead') and a hint for the source parameter. It stops short of exclusions or naming alternatives such as create_lead_source for channel management, so no explicit when-not guidance.

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

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