Skip to main content
Glama
Sign In
Product Manager MCP

Product Manager MCP

by r28ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

linear_users_list

Read-onlyIdempotent

List Linear workspace members and filter by name or email to resolve the UUID required for issue assignment.

Instructions

List workspace members. Use this to resolve a person's name or email to the UUID that assignment expects.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "linear_users_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
variablesNoPaging and filtering.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds the resolution use case but says nothing about pagination behavior or the rich filtering surface, leaving behavioral gaps the annotations don't fill.

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 tight sentences, front-loaded with the core action and followed by the practical use case. Every clause earns its place with no filler.

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 list tool with fully documented schema parameters and no output schema, the description covers purpose and usage adequately. It could mention pagination/filtering at a high level, but nothing critical for correct invocation is missing.

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 parameter, including the filter comparators and pagination fields. The description adds no syntax or semantic detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ('List workspace members') and immediately clarifies the practical purpose: resolving a person's name or email to the UUID that assignment expects. This distinguishes it from siblings like linear_issues_list or slack_users_list without ambiguity.

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?

Explicitly states when to use it ('to resolve a person's name or email to the UUID that assignment expects'), which is strong contextual guidance. It does not name an alternative tool or state when NOT to use it, so it falls short of a 5.

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