Skip to main content
Glama
Deepankar1993

Trello MCP Server - Optimized

search_members

Search Trello members by name or username to locate user profiles. Simplifies finding and managing board members with targeted queries.

Instructions

Search for members by name. Use this to find Trello users by their name or username.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (max 20, default: 8)
queryYesSearch query
fieldsNoSpecific fields to include in the response. Overrides detailLevel. Use dot notation for nested fields (e.g., 'prefs.permissionLevel')
maxItemsNoMaximum number of items to return for list operations. Helps reduce response size for large datasets
summarizeNoReturn summary information instead of full data for list operations (e.g., '50 cards' instead of full card array)
detailLevelNoResponse detail level. 'minimal' returns only essential fields, 'standard' returns commonly used fields, 'detailed' returns most fields, 'full' returns all fields (default varies by operation type)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the search action without revealing how matching works (e.g., partial vs. exact), whether results are read-only, or any response format details. This leaves significant behavioral ambiguity for an unannotated tool.

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?

The description is extremely concise, consisting of two sentences that immediately and clearly state the tool's purpose. Every word adds value, with no fluff or redundant information.

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 6 parameters and no output schema, the description only covers the basic search action. It does not explain what the response contains, how the search behaves, or how parameters like fields and detailLevel affect results. This leaves notable gaps in understanding the tool's full behavior.

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?

The input schema provides 100% parameter descriptions, so the baseline is 3. The description adds no additional parameter-specific meaning beyond what the schema already documents, and it doesn't clarify parameters like limit or detailLevel in the context of member search.

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 uses the specific verb 'Search' with the resource 'members' and clearly states the search criteria ('by name or username'). This distinguishes it from sibling tools like get_member or get_board_members, which serve different lookup and listing purposes.

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?

The description provides clear context for when to use the tool: 'Use this to find Trello users by their name or username.' However, it does not explicitly exclude alternatives or mention cases where other tools (e.g., get_member) might be more appropriate, such as when a user ID is already known.

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/Deepankar1993/trello-mcp-server-optimize'

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