Skip to main content
Glama

linear_getDocuments

Read-onlyIdempotent

Search and retrieve documents from your Linear workspace using filters like title, team, cycle, project, or issue. Sort results by creation or update date, and include archived documents.

Instructions

Get workspace documents from Linear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of documents to return (default: 25)
titleNoCase-insensitive title search filter
teamIdNoFilter documents by team ID
cycleIdNoFilter documents by cycle ID
issueIdNoFilter documents by issue ID
orderByNoSort documents by created or updated date
projectIdNoFilter documents by project ID
releaseIdNoFilter documents by release ID
initiativeIdNoFilter documents by initiative ID
includeArchivedNoInclude archived documents in the results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
Behavior2/5

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

Description adds no behavioral context beyond what annotations already provide. Annotations indicate read-only, idempotent, and non-destructive traits, but description does not elaborate on pagination, rate limits, or any side effects.

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?

Single sentence, no wasted words, but lacks necessary detail. Conciseness is good but at the expense of completeness.

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

Completeness2/5

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

Despite having output schema and annotations, the description is too minimal for a tool with 10 optional parameters and many sibling document retrieval tools. Does not explain how it differs from filtered versions.

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?

Input schema already has complete parameter descriptions (100% coverage), so description adds no additional semantic value. Baseline 3 is 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?

Description clearly states verb 'get' and resource 'workspace documents', but fails to differentiate from sibling tools like 'linear_getProjectDocuments' or 'linear_getTeamDocuments' which also get documents with specific filters.

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?

No guidance on when to use this tool versus more specific document retrieval tools. No mention of context, exclusions, or prerequisites.

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/tacticlaunch/mcp-linear'

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