PoliteReach

Create ICP

li_create_icp

Create an ICP (ideal customer profile) label to attach to campaigns, so li_outreach_analytics(groupBy="icp") can compare audiences. Only a label: it targets, filters and sends nothing. Check li_list_icps first — names are unique per team and a clash is refused. Dry-run unless confirmCreate=true; the confirmed call returns the new ICP with its id. It belongs to YOUR team (the reply's owner says whose). An operator credential with no team must name the account whose team owns it (sessionLabel) or pass shared:true; it is never published to every team by default.

Input Schema

Name	Required	Description
`name`	Yes	Label name, unique within your team (check li_list_icps first)
`shared`	No	Operator only: true publishes it as a shared template every team sees. Never the default.
`sessionId`	No	Operator only: the account whose TEAM owns it. Members' creates are their team's.
`description`	No	Optional note on who this audience is
`sessionLabel`	No	Operator only: the account whose TEAM owns it. Members' creates are their team's.
`confirmCreate`	Yes	Must be true to write the ICP to the database

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 14, 2026

addedInput schema / properties / sessionId

Added value: +{
+  "description": "Operator only: the account whose TEAM owns it. Members' creates are their team's.",
+  "type": "string"
+}

addedInput schema / properties / sessionLabel

Added value: +{
+  "description": "Operator only: the account whose TEAM owns it. Members' creates are their team's.",
+  "type": "string"
+}

addedInput schema / properties / shared

Added value: +{
+  "description": "Operator only: true publishes it as a shared template every team sees. Never the default.",
+  "type": "boolean"
+}

Changed2 schema fields changedOct 4, 2026
- addedInput schema / properties / description / description
```
Added value: +"Optional note on who this audience is"
```
- addedInput schema / properties / name / description
```
Added value: +"Label name, unique within your team (check li_list_icps first)"
```
First observedOct 3, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: dry-run-by-default, the confirmCreate gate, that the confirmed call returns the new ICP with its `id`, team ownership of the created object, and the operator-credential edge case (must supply sessionLabel or shared:true, never published to every team by default). These are exactly the non-obvious traits an agent needs and none are derivable from the readOnlyHint/destructiveHint flags.

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 and the "only a label" scope, then proceeds to warnings and edge cases. It is dense and slightly long, but each sentence carries a distinct constraint (uniqueness, dry-run, ownership, operator handling), so little is wasted.

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?

For a mutation tool with no output schema, the description supplies the missing return information ("returns the new ICP with its `id`"), the safety/confirmation model, and the credential-dependent ownership behavior. Together with the annotations, an agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter logic the schema states only piecemeal: it ties sessionLabel and shared:true together as the alternatives an operator with no team must choose between, and reinforces the uniqueness constraint on `name` and the write-gate on confirmCreate.

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 ("Create an ICP (ideal customer profile) label") and immediately explains its downstream purpose (attaching to campaigns so li_outreach_analytics(groupBy="icp") can compare audiences). The clarification "Only a label: it targets, filters and sends nothing" sharply distinguishes it from campaign/outreach siblings.

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

Usage Guidelines5/5

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

Gives explicit preconditions and alternatives: "Check li_list_icps first — names are unique per team and a clash is refused" and "Dry-run unless confirmCreate=true." It names the sibling to consult and the exact gate that switches the tool from dry-run to a real write.

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

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