Skip to main content
Glama
Sign In
Coherence XRM

Coherence XRM

Official
by getcoherence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_outreach_items

List outreach content items such as blog articles, LinkedIn posts, and emails, with filters by type and status.

Instructions

List outreach content items (blog articles, LinkedIn posts, emails). Filter by type and status.

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_outreach_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by content type
statusNoFilter by status
pageNoPage number
pageSizeNoItems per page
searchNoSearch by title

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided; description does not disclose read-only nature, pagination behavior, or any side effects. For a listing tool, minimal behavioral context is given.

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?

Single sentence that is concise and front-loaded with the key action and resource. No superfluous words.

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

Completeness2/5

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

No output schema; description does not mention return format, pagination, or ordering. For a paginated list tool, this is insufficient for an agent to fully understand the response.

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 provides 100% coverage with descriptions for all parameters. Description adds no additional meaning beyond 'Filter by type and status', which is already in schema. Baseline score of 3 applies.

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 it lists outreach items and specifies sub-types (blog articles, LinkedIn posts, emails). It distinguishes from sibling tools like get_outreach_item (single) and create_outreach_item.

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?

Implies usage for listing with filters, but no explicit when-to-use vs alternatives like search or pagination details. No exclusions mentioned.

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

Deploy Server

Other Tools