Linkbreakers MCP

Create Agent

agents_create

Create an agent: a chat persona with a role, tone, guardrails and knowledge that talks to visitors from workflow steps such as the Chat Bot step.

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

Input Schema

Name	Required	Description
`name`	Yes	The agent's name.
`role`	No	The job the agent does.
`tone`	No	How the agent sounds.
`language`	No	ISO 639-1 code of the language the agent always speaks. Empty matches the visitor's language.
`guardrails`	No	The preset rules the agent never breaks. Leave empty for the defaults.
`styleNotes`	No	Free-text notes that refine the tone.
`customRules`	No	Free-text rules the agent never breaks.
`replyLength`	No	How long the agent's messages are.
`emojiEnabled`	No	Whether the agent may use emoji. Off when unset.
`instructions`	No	Free-text instructions that refine the role.
`questionHandling`	No	What the agent does when a visitor asks it something.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It explains what an agent conceptually is and where it is used, but it does not disclose creation side effects, required permissions, default state, whether the agent is immediately active, or what the response contains.

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 definition is a single front-loaded sentence with no filler. It states the action first and then supplies the minimum domain context needed to understand what is being created.

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?

The schema is rich and fully documented, which covers the parameter surface well. However, with 11 parameters, no annotations, and no output schema, the description is only minimally adequate: it omits creation semantics, defaults, permissions, and return behavior.

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 description coverage is 100%, so all 11 parameters are already well documented in the input schema. The description mentions role, tone, and guardrails, but adds no syntax, defaults, enum distinctions, or other meaning beyond what the schema already provides.

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?

The description gives a specific verb and resource: 'Create an agent,' and further defines an agent as a chat persona with a role, tone, guardrails, and knowledge. This clearly separates creation from agents_get, agents_list, agents_update, and agents_delete, though it does not explicitly name those siblings.

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

Usage Guidelines3/5

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

It implies the tool is used when an agent is needed to talk to visitors from workflow steps such as the Chat Bot step. However, it gives no explicit when-to-use/when-not-to-use guidance, no prerequisites, and no comparison to agents_update or agents_list_presets.

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

All Linkbreakers MCP 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.