Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

algolia_browse_index

Browse all records from an Algolia index with cursor-based pagination. Apply filters, set hits per page, and retrieve specific attributes.

Instructions

Browse all records in an Algolia index (paginated cursor-based).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app_id": "<app_id>",
      "api_key": "<api_key>",
      "index": "<index>"
    },
    "name": "algolia_browse_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYesIndex name
app_idYesAlgolia Application ID
cursorNoPagination cursor from previous response
api_keyYesAlgolia Admin API Key
filtersNoFilter expression
hits_per_pageNoRecords per page
attributes_to_retrieveNoAttributes to include

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.9
  2. Removed
  3. Addedv0.1.5

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only mentions pagination (cursor-based), but doesn't disclose read-only nature, auth expectations, rate limits, or handling of large datasets. For a browse operation, more behavioral context is needed.

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?

Single front-loaded sentence with verb, resource, and key feature (pagination). No redundant words, efficient and to the point.

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 7 parameters and no output schema, the description is minimal. It doesn't explain cursor-based pagination fully, nor does it mention performance implications, error handling, or result format. More context would aid agent decision-making.

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 parameter descriptions. The description adds no additional meaning beyond what's in the schema. Baseline 3 is appropriate as schema does the heavy lifting.

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 verb 'Browse', the resource 'all records in an Algolia index', and notes pagination style 'paginated cursor-based'. This distinguishes it from siblings like algolia_search (search) and algolia_get_object (single object).

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?

No explicit when-to-use or when-not-to-use guidance. It implies use when you need all records, but doesn't compare to alternatives like algolia_search for filtered browsing. The context is clear but lacks exclusions.

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