Skip to main content
Glama

List Companies

hudu_list_companies
Read-onlyIdempotent

List companies in Hudu, filtering by name, search, city, state, and more. Paginate through results to retrieve complete data with pagination details.

Instructions

List companies in Hudu. A company is the top-level container in Hudu; every asset, article, password and website belongs to exactly one.

To find a company by name, prefer search (matches broadly) over name (matches the name field). If the API key was created with a company scope, only that company is visible here and everything else returns 404.

Returns an object with items plus pagination facts. Note that the Hudu API returns no total count for any collection, so page_was_full is the only honest signal that more records exist — read pagination_note before concluding a list is complete.

Operation class: Read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNo
nameNoMatch against the company name specifically.
pageNo1-based page number. Hudu has no cursor or offset — only pages.
slugNoURL slug, if you already know it.
stateNo
fieldsNoReturn only these top-level fields on each record. Use it to keep large lists small — e.g. ["id","name","company_id"]. Unknown field names are ignored.
searchNoBroad text search across company fields. The best first filter for a name.
websiteNo
id_numberNoYour own external identifier.
page_sizeNoRecords per page (1-100, default 25). Hudu publishes no maximum, so this client clamps at 100; larger values are rejected here rather than silently altered by the server.
updated_atNoISO-8601 range as "start,end". Either side may be omitted — "2026-01-01T00:00:00Z," means everything changed since that moment.
phone_numberNo
response_formatNoOutput shape. 'json' (default) is compact and machine-readable; 'markdown' is easier for a person to read but larger.json
id_in_integrationNoMatch a company by its id inside a connected integration (PSA, RMM).
Behavior5/5

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

Annotations already signal read-only, idempotent, and open-world behavior, but the description adds vital details: the Hudu API returns no total count, 'page_was_full' is the only honest pagination signal, and scoped keys cause 404s. These go beyond the annotations and materially shape how the agent should interpret results.

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?

The description is a few focused paragraphs with front-loaded purpose. The final 'Operation class: Read' is redundant given readOnlyHint=true, but the rest of the content is efficiently ordered and each sentence provides distinct information about the tool's quirks and usage.

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?

Given the tool has 14 parameters, no output schema, and significant pagination quirks, the description covers the essential context: return shape, pagination honesty, scoping constraints, and key filter guidance. It does not need to repeat schema details, and the missing pieces (e.g., exact field list) are not critical for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 71%, and the description adds semantic value by distinguishing 'search' (broad) from 'name' (exact field) and explaining the clamped page_size behavior. This is extra guidance beyond the schema's per-parameter descriptions, though the schema already carries most of the parameter intent.

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 opens with 'List companies in Hudu', a specific verb+resource statement, and clarifies that a company is the top-level container in Hudu. This makes the tool's purpose unambiguous and distinct from sibling get/list tools by naming the exact resource and action.

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 in-tool guidance: 'prefer search over name' for finding by name, and warns that a company-scoped API key only exposes that company (everything else 404). It does not explicitly name alternatives like hudu_get_company, but offers enough contextual usage direction to guide the agent.

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/ZenixSolutions/hudu-mcp'

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