Skip to main content
Glama
Sign In
agenthouse-org

dealdesk-mcp

by agenthouse-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

dealdesk.list_status_updates

Lists status updates, comments, tasks, and email touchpoints for a desk card, company, or contact so you can review activity in one timeline.

Instructions

List status updates (comments, tasks, touchpoints including email) for a desk card, company, or contact.

Input Schema

NameRequiredDescriptionDefault
limitNo
cardIdNoAlias for entityId when entityType is desk-card
entityIdNoCard id, company id, or contact id
projectIdNoDealDesk project id. Omit when the OAuth token or API key authorizes exactly one project. Required when Connect authorized several projects.
entityTypeNoEntity the timeline is scoped to (default desk-card)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / projectId / description
      Previous value: -"DealDesk project id (must match API key / OAuth project)"New value: +"DealDesk project id. Omit when the OAuth token or API key authorizes exactly one project. Required when Connect authorized several projects."
    • changedInput schema / required
      Previous value: -[
-  "projectId"
-]New value: +[]
  2. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It indicates the kinds of items returned (comments, tasks, touchpoints including email), but does not disclose pagination behavior, permissions, ordering, or other operational traits an agent may need.

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 definition is a single, front-loaded sentence with no wasted words. It states the core action and scope immediately.

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?

The description covers the tool's scope and entity types, which matches the higher-level purpose. However, with no annotations and no output schema, it leaves behavioral gaps around pagination, return shape, and selection relative to siblings, making it only minimally 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 80%, so the schema already documents most parameters, including entityType, entityId, cardId, and projectId. The description adds no parameter-level details beyond what the schema provides, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('List') and resource ('status updates'), and clarifies the scope as desk cards, companies, or contacts. It does not explicitly distinguish itself from related siblings such as list_card_activity or create_status_update, so sibling differentiation is only partial.

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?

The description states what can be listed but gives no explicit when-to-use guidance or alternatives. It does not explain when to choose this tool over list_card_activity, get_card, or other related status update endpoints.

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