Skip to main content
Glama
Sign In

Goptin

by com.goptin.app
OverviewDiscussionsAdmin

get_ticket

Read-only

Get one ticket live: full description, status, assignees, tags, parent, subtasks, linked tickets, attachments (with URLs), plus comments. Pass ticket_id (and account_id when you have several boards) from list_tickets, or a conversation_id. Synced tickets return the inbox thread including status/assignee/due-date change events.

Input Schema

NameRequiredDescriptionDefault
ticket_idNoticket_id (ClickUp) or key (Jira, e.g. SCRUM-3)
account_idNoaccount_id of the Jira/ClickUp board (from list_tickets)
comment_limitNoDefault 20, max 100
conversation_idNoThe ticket's conversation_id, when list_tickets returned one
max_descriptionNoTruncate the description to this many characters (default: full)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "account_id of the Jira/ClickUp board (from list_tickets)",
+  "type": "string"
+}
    • addedInput schema / properties / conversation_id / description
      Added value: +"The ticket's conversation_id, when list_tickets returned one"
    • addedInput schema / properties / max_description
      Added value: +{
+  "description": "Truncate the description to this many characters (default: full)",
+  "type": "number"
+}
    • addedInput schema / properties / ticket_id
      Added value: +{
+  "description": "ticket_id (ClickUp) or key (Jira, e.g. SCRUM-3)",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "conversation_id"
-]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description still earns credit by disclosing that data is fetched "live" and that synced tickets return the inbox thread with status/assignee/due-date change events — non-obvious return-shape behavior. It does not mention cost/latency of pulling attachments and comments on every call, which would have completed the picture.

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?

Two sentences, zero filler, with the return payload front-loaded ahead of the invocation guidance and the synced-ticket edge case last. Every clause carries distinct information.

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

Completeness5/5

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

No output schema exists, yet the description effectively documents the return surface (fields, attachments with URLs, comments, change events), and it explains both ID sourcing paths. For a read-only single-entity fetch with fully documented parameters, nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine semantics beyond it: that ticket_id/account_id originate from list_tickets, that account_id only matters across multiple boards, and that conversation_id is an alternative lookup path. The truncation and comment_limit parameters are left to the schema, which is acceptable at full coverage.

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?

Opens with a specific verb+resource ("Get one ticket") and then enumerates exactly what a "live" fetch returns: description, status, assignees, tags, parent, subtasks, linked tickets, attachments with URLs, comments. The singular framing plus the explicit pointer to list_tickets makes it immediately distinguishable from the sibling list/comment tools.

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?

Gives concrete routing: fetch by ticket_id sourced from list_tickets, add account_id when multiple boards exist, or use conversation_id instead. That covers the realistic alternatives well, but there is no explicit statement of when *not* to use this (e.g. bulk retrieval, or when only comment counts are needed).

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

All Goptin toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources