Skip to main content
Glama
mcp-server-smartsheet-rm

mcp-server-smartsheet-rm

Projects List Relationships Project Memberships

projects_list_relationships_project_memberships
Read-onlyIdempotent

List project memberships for specified users or filter by membership level to identify project access assignments.

Instructions

List project memberships for one or more users.

OpenAPI: GET /relationships/project_memberships (getRelationshipsProjectMemberships). user_ids is a comma-separated list of user IDs when provided. When omitted, membership defaults to member; pass another level to list those.

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": "projects_list_relationships_project_memberships"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResponse page to return, starting at 1 (default 1).
per_pageNoMaximum items per page, up to 1000 (default 20).
user_idsNoOptional comma-separated IDs of the users whose memberships to list.
membershipNoMembership level to list: member, viewer, reporter, scheduler or editor.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent read (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description adds one genuinely useful behavioral fact not in the structured data: an implicit server-side default that resolves membership to 'member' in some omitted case. That sentence is ambiguously worded (unclear whether 'omitted' refers to user_ids or membership), and pagination/result-shape behavior is not mentioned.

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?

Short and generally front-loaded, with purpose first and constraints after. The OpenAPI line is somewhat incidental, and the final sentence's referent for 'omitted' is unclear enough to need a re-read, but there is little outright waste.

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

Completeness3/5

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

With four optional params, full schema coverage, complete annotations, and an output schema, most of the burden is already carried by structured fields. What remains unaddressed is sibling differentiation and paging behavior, and the one behavioral caveat it does offer is phrased ambiguously.

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 baseline is 3; the schema already documents page, per_page, the comma-separated user_ids format, and the membership levels. The description restates the comma-separated format and adds only the default-fallback note for membership, which is marginal added meaning over the schema.

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 and resource: 'List project memberships for one or more users.' The 'for one or more users' scope differentiates it somewhat from the many other project-membership listing siblings, but it never names or contrasts with projects_list_project_members or projects_list_relationships_project_members, so the boundary is left implicit.

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?

Gives conditional guidance about the user_ids and membership parameters ('when provided', 'when omitted... defaults to member'), which is parameter behavior rather than tool-selection guidance. It never says when to choose this tool over the several other membership-listing siblings.

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