Skip to main content
Glama

retrieve_entities

Retrieve filtered entity lists by type, pagination, and date filters, or perform lexical/semantic search across versioned entities.

Instructions

Use this when you need filtered entity lists (by type, pagination, and optional published/date filters) or lexical/semantic retrieval via search. Strict mode: search cannot be combined with non-default sorting or published filters. Set include_snapshots=false for lightweight responses that omit snapshot/provenance/raw_fragments. Compatibility aliases search_query and query are accepted but search is canonical.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_typeNoOptional entity type filter (for example: post, task, contact).
searchNoCanonical free-text query for lexical/semantic retrieval. Cannot be combined with published filters or non-default sorting.
search_queryNoCompatibility alias for `search`.
queryNoCompatibility alias for `search`.
similarity_thresholdNoSemantic distance threshold when `search` is used. Lower is stricter (typical 1.0-1.05).
limitNoMaximum number of entities to return (default 100).
offsetNoPagination offset (default 0).
sort_byNoSort field. Non-default values cannot be combined with `search`.
sort_orderNoSort direction. `desc` cannot be combined with `search`.
publishedNoFilter by snapshot.published. Cannot be combined with `search`.
published_afterNoInclusive lower bound for snapshot.published_date (ISO date/datetime). Cannot be combined with `search`.
published_beforeNoInclusive upper bound for snapshot.published_date (ISO date/datetime). Cannot be combined with `search`.
include_snapshotsNoWhen false, omit snapshot/provenance/raw_fragments payloads for lightweight responses.
include_mergedNoWhether to include merged entities (default false).
user_idNoOptional explicit user ID (normally inferred from auth context).
updated_sinceNoISO 8601 timestamp. Return only entities whose updated_at is greater than or equal to this value.
created_sinceNoISO 8601 timestamp. Return only entities whose created_at is greater than or equal to this value.
exclude_bookkeepingNoWhen true, omit chat bookkeeping types (`conversation`, `conversation_message`, etc.) from results. Default false. Has no effect when `entity_type` already filters to a bookkeeping type.
Behavior4/5

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

With no annotations, the description discloses key behavioral traits: strict mode constraints, alias handling, and the effect of include_snapshots. It also mentions that user_id is normally inferred from auth. However, it does not discuss rate limits, error handling, or security aspects.

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?

Two sentences, front-loaded with the main use case. Every word adds value: no fluff, clear structure. The constraints and options are stated efficiently.

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's complexity (18 parameters, no output schema), the description covers core use cases, constraints, performance tip, and alias. It does not explain return format, but the high schema coverage compensates. Mostly complete.

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 coverage is 100%, but the description adds value by aggregating constraints (e.g., search cannot combine with published/sorting) and explaining aliases and include_snapshots. This provides practical context beyond the individual parameter descriptions.

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?

The description clearly states it retrieves filtered entity lists with type, pagination, date filters, and lexical/semantic search. It does not explicitly differentiate from sibling tools like retrieve_entity_by_identifier, but the purpose is unambiguous.

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 guidance on when to use (filtered lists or search) and constraints (search cannot combine with published filters or non-default sorting). It mentions compatibility aliases and include_snapshots options, but lacks explicit 'when not to use' or alternatives besides the sibling list.

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/markmhendrickson/neotoma'

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