Skip to main content
Glama
bruhsb

paperclip-mcp

by bruhsb
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

paperclip_create_issue

Create a new issue in your company, specifying title, description, status, priority, and associations. Returns the created issue with its identifier.

Instructions

Create a new issue in the current company.

Args:

  • title: string — Issue title (required)

  • description: string (optional) — Issue description (markdown)

  • status: enum (optional) — Initial status; pass 'backlog' explicitly (API default is todo)

  • priority: enum (optional) — Priority: critical | high | medium | low

  • parentId: string (optional) — Parent issue UUID for sub-tasks

  • goalId: string (optional) — Goal UUID to link the issue

  • projectId: string (optional) — Project UUID to associate

  • assigneeAgentId: string (optional) — Assignee agent UUID

  • billingCode: string (optional) — Billing code for cost tracking

  • labelIds: string[] (optional) — Label UUIDs to apply

  • inheritExecutionWorkspaceFromIssueId: string (optional) — Inherit workspace from another issue

Returns: Returns the created issue object with all fields including the assigned identifier (e.g. PAP-42).

Examples:

  • Use when: filing a new bug, MCP tool failure, or gap discovered mid-run for Scrum Master to triage

  • Don't use when: the issue already exists — use paperclip_update_issue to modify it

Error Handling:

  • 400: validation failure → ensure title is non-empty and status/priority are valid enums

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 404: referenced goalId or projectId not found → verify with paperclip_list_goals or paperclip_list_projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesIssue title
descriptionNoIssue description (markdown)
statusNoInitial status (default: backlog)
priorityNoPriority level
parentIdNoParent issue UUID
goalIdNoGoal UUID to link the issue to
projectIdNoProject UUID to associate
assigneeAgentIdNoAssignee agent UUID
billingCodeNoBilling code for cost tracking
labelIdsNoLabel UUIDs to apply
inheritExecutionWorkspaceFromIssueIdNoLink to an existing execution workspace (for follow-up tasks on same checkout)

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

Annotations only indicate destructiveHint=false and openWorldHint=false. The description discloses return behavior (returns created issue object with identifier) and error codes for 400, 401, 404. No contradiction, but lacks details on side effects beyond creation.

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?

Well-organized with separate sections for Args, Returns, Examples, and Error Handling. Every sentence adds value, no repetition of schema. Concise yet comprehensive.

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?

Addresses all key aspects: purpose, parameters, usage context, return type, and error scenarios. Despite 11 parameters and no output schema, description fully compensates with clear return description and examples.

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%, baseline 3. Description adds value beyond schema by clarifying default status behavior ('pass 'backlog' explicitly (API default is todo)') and explaining inheritExecutionWorkspaceFromIssueId ('for follow-up tasks on same checkout').

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 'Create a new issue in the current company', specifying the action, resource, and scope. It distinguishes from sibling 'paperclip_update_issue' by explicitly noting when not to use this tool.

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

Usage Guidelines5/5

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

Provides explicit 'Use when' and 'Don't use when' examples, including a direct alternative ('use paperclip_update_issue to modify it'). Also includes error handling with actionable remediation steps.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bruhsb/paperclip-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server