Skip to main content
Glama
Sign In

Emailchaser

by com.emailchaser
OverviewDiscussionsAdmin

List ICPs

list_icps
Read-only

Lists the workspace's stored Ideal Customer Profiles (ICPs), newest first, with their targeting criteria, whether each is AI-generated or human-edited, and the estimated audience size.

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": "list_icps"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1
limitNoPage size (default 50, max 200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile needs no repetition. The description contributes behavior the annotations do not: a deterministic sort order (newest first) and the composition of each returned record, including the AI-generated vs human-edited provenance flag and an estimated audience size.

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?

A single sentence with the resource identified first, then ordering, then record contents. Every clause carries information an agent cannot get from the name alone, and there is no filler or repetition of the title.

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?

With no output schema, the description usefully enumerates the salient returned fields and the sort order, which is exactly what an agent needs to interpret results. It stops short of describing envelope details such as total counts or how to detect the last page, but for a two-optional-parameter read tool this is close to complete.

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% — page and limit are both documented, with limit's default and maximum spelled out in the schema — so the baseline of 3 applies. The description adds nothing about paging semantics (e.g. whether paging is over a stable newest-first order) and does not mention the parameters at all.

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 opens with a specific verb and resource ("Lists the workspace's stored Ideal Customer Profiles") and immediately scopes it further with ordering ("newest first") and the fields returned (targeting criteria, AI-generated vs human-edited, audience size). That is enough for an agent to distinguish it from the other list_* siblings, which all address different resources.

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?

The imperative "Lists" plus the "stored" qualifier implies this is a read of existing ICPs, but there is no explicit when-to-use guidance, no mention of alternatives (e.g. any tool that creates or updates ICPs), and no note that no filtering is supported beyond paging. Usage is inferable rather than stated.

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

All Emailchaser toolsInspect
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