Skip to main content
Glama

raisely

by io.usefulapi

List users

list_users
Read-only

List users (donors/supporters/fundraisers). Raisely API: GET /users. Filter via params. Returns { data:[...], pagination }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax records to return (Raisely `limit`, default 20).
offsetNoRecords to skip for pagination (Raisely `offset`, default 0).
paramsNoAdditional documented query-string filters to send verbatim (e.g. campaign, status, sort, order, private) — merged with the typed limit/offset above.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The readOnlyHint annotation already indicates a safe read operation. The description adds value by specifying the HTTP GET method and the return shape ({ data:[...], pagination }), providing useful context about what to expect. No contradiction with annotations.

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 a single, well-structured sentence that front-loads the primary verb and resource. It includes the API endpoint and return format without any unnecessary fluff.

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

Completeness5/5

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

For a list operation, the description is complete: it states the resource, the API endpoint, filtering mechanism, and return structure. Even without an output schema, the agent has sufficient context to invoke the tool appropriately.

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 coverage is 100% with detailed descriptions for limit, offset, and params. The description's mention of 'Filter via `params`' adds no additional information beyond the schema, which already explains the params object and its use.

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 clearly states the tool's function: 'List users (donors/supporters/fundraisers)'. It distinguishes from siblings like get_user (single user) and list_profiles by specifying the user resource and the GET /users endpoint.

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—when a list of users is needed—but does not explicitly mention alternatives or exclusions. The sibling tools like get_user and list_profiles imply different use cases, but this description does not spell them out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All raisely toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool is clearly scoped to a specific resource and action. The get_/list_/create_/update_ prefixes distinguish reads from mutations, and the convenience listers are explicitly labeled, so there is no real overlap or confusion.

Naming Consistency4/5

Tool names largely follow a consistent verb_noun pattern (create_, get_, list_, update_). The only outlier is raisely_request, which is a generic escape hatch but breaks the pattern slightly.

Tool Count3/5

With 23 tools, the server is on the heavy side. While each tool maps to a distinct API endpoint, several convenience wrappers (list_campaign_donations, list_user_donations) add redundancy without significantly expanding functionality.

Completeness2/5

The tool surface is heavily read-oriented. Many core resources like campaigns, subscriptions, posts, and orders lack create/update/delete operations, and the read-only raisely_request cannot fill these gaps, leaving agents unable to perform common management tasks.

Resources