Skip to main content
Glama
Sign In
Product Manager MCP

Product Manager MCP

by r28ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

linear_document_create

Create a Linear document with only a title required, and optionally attach it to a project, initiative, issue, cycle, or team.

Instructions

Create a document. Only title is required — a document can hang off a project, initiative, issue, cycle or team, or off nothing at all.

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": {
      "variables": "<variables>"
    },
    "name": "linear_document_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
variablesYesThe document to create.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the write/open-world nature is covered. The description adds the meaningful behavioral fact that only `title` is mandatory and that parentage is optional, but says nothing about permissions, defaults applied, or side effects like subscriber notification.

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?

Two short sentences, front-loaded with the core action and then the key constraint about required vs. optional linkage. No filler, though the second sentence mixes a requirement statement with an enumeration of parent types.

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 a single-object create tool with full schema coverage and no output schema, the description supplies the essential call-shaping information (only title required, optional attachment targets). It is close to complete, with only auth/permission expectations left unstated.

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 the schema already documents every field. The description reinforces the required/optional split for `title` and the parent-link options, which is mild added value but not new syntax or format detail beyond the schema. Baseline 3 applies.

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?

States a specific verb+resource ('Create a document') that is clearly distinct from sibling creation tools like linear_issue_create or linear_project_create. It does not explicitly name or contrast siblings, but the resource noun is unambiguous.

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

Usage Guidelines3/5

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

The description gives useful usage context — only `title` is required and the document may attach to a project, initiative, issue, cycle, team, or nothing — which tells the agent the tool is flexible about parentage. However, it offers no when-to-use vs. when-not guidance or alternative tooling for creating content elsewhere.

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