Skip to main content
Glama
Sign In
Coherence XRM

Coherence XRM

Official
by getcoherence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_outreach_item

Create blog articles, LinkedIn posts, or emails as outreach items with status and scheduling. Returns the new item's ID.

Instructions

Create a new outreach content item (blog article, LinkedIn post, email). Returns the created item ID.

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": {
      "type": "<type>",
      "title": "<title>"
    },
    "name": "create_outreach_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesContent type
titleYesTitle of the content item
contentNoMDX/markdown content body
statusNoInitial status (default: draft)draft
socialConnectionIdNoSocialConnectionId — which connected social account to post as
scheduledForNoISO date-time for scheduled publication (e.g. '2026-04-01T14:00:00Z')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

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 must disclose behavioral traits. It only says 'creates' and 'returns ID', but omits potential side effects, permissions required, error conditions, or whether the action is destructive. Minimal transparency.

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 description is a single sentence that efficiently conveys the core purpose and return value. No unnecessary words or repetition.

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?

Given no output schema, the description mentions the return (ID) but does not elaborate on required fields, validation rules, or relationship to other outreach tools. It is minimally complete but lacks depth for complex usage.

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?

The input schema has 100% coverage with descriptions for all 6 parameters. The description adds no additional parameter-level meaning beyond 'returns created item ID', which is generic. Baseline 3 is appropriate as schema does the heavy lifting.

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 the verb (create), the resource (outreach content item), and provides specific examples (blog article, LinkedIn post, email). It distinguishes from sibling tools that get, update, list, or delete such items.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus siblings like create_record, or what prerequisites (e.g., account setup) are needed. The context for choosing this over alternatives is missing.

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