Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

Crm timeline

crm_timeline
Read-only

Reads one contact's history: the contact (id, kind, name, stage and why it may not be contacted, if so; for someone who signed up with the business, person, as crm_search gives it, and their address only when the owner is the one asking) and every touch with them, oldest first, each with its time, direction (out from the business, or in), channel, kind (pitch, email, reply, dm, comment, order, sign-up, unsubscribe, quote, placement, bounce, complaint, deal), summary and the work id it belonged to. Use it after crm_search to answer what happened with someone; an unknown id is refused.

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

Input Schema

NameRequiredDescriptionDefault
projectNoThe project's id or exact name. Optional when the account has one project.
contactIdYesThe contact's id, as crm_search gives it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, and closed-world behavior, so the description does not need to repeat that. It adds useful context beyond annotations: results are oldest first, address visibility depends on whether the owner is asking, and unknown ids are refused.

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?

The key purpose is front-loaded in the opening clause, and the long enumeration of contact and touch fields is largely justified by the complexity of the return shape. However, it is a single dense sentence that could be easier to scan if split into purpose, return, and usage segments.

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?

There is no output schema, so the description must carry return-value meaning, and it does explain the contact record and each touch's fields in detail. It is nearly complete for an agent to call the tool, with only the optional project parameter left underexplained in prose.

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 both parameters are already documented in the schema. The description reinforces that contactId comes from crm_search, but it does not explain the project parameter's role or interaction with contact history, so it stays at the baseline.

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 states a specific verb and resource: it reads one contact's history, including the contact fields and every touch in chronological order. It goes further by enumerating the returned touch fields (time, direction, channel, kind, summary, work id), making it clearly distinguishable from crm_search.

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

Usage Guidelines4/5

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

It explicitly says to use this after crm_search to answer what happened with someone, and notes that an unknown id is refused. It does not mention when not to use it or name an alternative such as timeline_query, so it falls short of full alternative-routing guidance.

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

All Marsell 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