Goptin

create_ticket

Create a ClickUp ticket as the user: a subtask under parent_ticket_id (it goes into the parent's list), or a new ticket in a list. Returns ticket_id and url. The team sees it — show the user the title, description and assignees and confirm first. Jira is not supported yet.

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": {
      "account_id": "<account_id>",
      "title": "<title>"
    },
    "name": "create_ticket"
  }
}

Input Schema

Name	Required	Description
`list`	No	List id or name fragment (e.g. "Sprint 102"); optional when parent_ticket_id is given
`title`	Yes
`status`	No	Initial status name (must exist in the list)
`due_date`	No	YYYY-MM-DD
`assignees`	No	ClickUp user ids or names, matched against the list's members
`account_id`	Yes	The ClickUp account_id (from list_accounts or list_tickets)
`description`	No	Markdown
`parent_ticket_id`	No	Make it a subtask of this ClickUp ticket_id (inherits the parent's list)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), it discloses that the ticket is visible to the whole team, that the returned values are ticket_id and url, and that Jira is unsupported. It stops short of stating auth/permission requirements or rate limits for an open-world mutation.

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?

Three tight sentences with the primary action front-loaded, then the branching mode, then the return and safety guidance. No filler or redundancy.

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?

For an 8-parameter mutation with no output schema, it covers both creation modes, the return values, and the confirmation workflow. The remaining gap is the unresolved overlap with the sibling create_task, which matters for tool selection.

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 coverage is 88%, so the schema already documents most parameters well. The description adds relational meaning by explaining that parent_ticket_id makes a subtask and that list becomes optional in that case, but little beyond what the schema fields already say.

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 states a specific verb and resource ("Create a ClickUp ticket") and distinguishes its two modes: a subtask under parent_ticket_id versus a new ticket in a list. It does not, however, differentiate itself from the sibling create_task, so an agent must guess which creation tool is appropriate.

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 gives clear operating context — when parent_ticket_id is supplied the ticket becomes a subtask, otherwise a list is used, plus an explicit workflow instruction to confirm with the user before creating. It lacks an explicit exclusion or pointer to the sibling create_task as the alternative.

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

All Goptin tools Inspect

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

Need Help?