Skip to main content
Glama
Sign In
nubiia-dev

MCP Holded

by nubiia-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_contact_groups

Retrieve Holded contact groups with cursor-based pagination. Control page size, project specific fields, or return only counts and pagination metadata to reduce response size.

Instructions

List contact groups (Holded API v2). Cursor-paginated: pass the previous response nextCursor as cursor. Response fields are snake_case; amounts are strings with decimal comma.

Input Schema

NameRequiredDescriptionDefault
limitNoMax items per page (server-paginated; use limit to control page size)
cursorNoCursor from a previous response nextCursor
fieldsNoProject only these fields per item (e.g. ["id", "name"]). Reduces response size.
summaryNoReturn only count and pagination metadata without items (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.0.3
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Cursor from a previous response nextCursor",
+  "type": "string"
+}
    • changedInput schema / properties / fields / description
      Previous value: -"Select specific fields to return (e.g., [\"id\", \"name\"]). Reduces response size by 70-90%. If not provided, returns default fields: id, name"New value: +"Project only these fields per item (e.g. [\"id\", \"name\"]). Reduces response size."
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max items per page (server-paginated; use limit to control page size)",
+  "type": "number"
+}
    • removedInput schema / properties / page
      Removed value: -{
-  "description": "Page number (starting from 1, default: 1)",
-  "type": "number"
-}
    • removedInput schema / properties / pageSize
      Removed value: -{
-  "description": "Number of items per page (default: 50, max: 500)",
-  "type": "number"
-}
    • changedInput schema / properties / summary / description
      Previous value: -"Return only total count and page count without items (default: false)"New value: +"Return only count and pagination metadata without items (default: false)"
  2. First observedv1.6.0

TDQS

B3.3/5.0
Behavior3/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. It usefully discloses cursor pagination and response conventions (snake_case fields, decimal-comma amounts), but omits permissions, rate limits, and full return shape.

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?

Three compact sentences, front-loaded with purpose, then pagination, then response-format caveats. No filler or repetition.

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?

There is no output schema, so the description should explain return values more fully. It gives response formatting hints but does not describe the items/count/nextCursor structure, leaving a meaningful gap for a list endpoint.

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 all four parameters. The description only reiterates that cursor comes from nextCursor and does not add meaning for limit, fields, or summary beyond 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 contact groups', plus API version. The listing verb distinguishes it from create/get/update/delete_contact_group siblings, but it does not explicitly route to get_contact_group or list_contacts.

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?

Provides pagination mechanics but no when-to-use guidance or alternatives. It does not say when to use this instead of get_contact_group for a single group or list_contacts for contacts.

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