Skip to main content
Glama

GetCollectionAssets

Get assets in a collection with membership metadata (position, role, added date). For a query-backed collection (collection_kind "query") the assets are the current matches of its saved query, newest first; include_nested and order_by do not apply.

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": {
      "collection_path": "<collection_path>"
    },
    "name": "GetCollectionAssets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of assets to return. Default: 50
offsetNoOffset for pagination. Default: 0
order_byNoSort order: "position" or "added_at". Default: "position"position
tenant_idNoOptional: UUID of the tenant. Omit it: the server uses the tenant your credential (OAuth connection or API key) is bound to. A tenant_id that differs from the credential's tenant is rejected.
include_nestedNoInclude assets from all descendant collections. Default: false
collection_pathYesCollection ltree path to get assets from

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / tenant_id / description
      Previous value: -"UUID of the tenant"New value: +"Optional: UUID of the tenant. Omit it: the server uses the tenant your credential (OAuth connection or API key) is bound to. A tenant_id that differs from the credential's tenant is rejected."
    • changedInput schema / required
      Previous value: -[
      -  "tenant_id",
      -  "collection_path"
      -]New value: +[
      +  "collection_path"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and delivers the non-obvious parts: what metadata ships with each asset and the special semantics of query-backed collections (current matches, newest first, ignored parameters). It does not cover permission requirements, behavior on missing/invalid collection paths, or empty-result cases, which keeps it below a 5.

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 primary purpose followed immediately by the exception case. Every clause carries information not present in the name or schema; nothing is padding.

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?

There is no output schema and no annotations, so the description must convey what comes back, and it does by enumerating the membership metadata fields. The query-collection carve-out prevents a plausible misuse of order_by/include_nested. Remaining gaps (pagination interaction with query collections, error behavior) are minor for a read tool.

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 all six parameters including limit/offset defaults and the order_by enum are already documented in the schema, establishing a baseline of 3. The description adds one real piece of meaning beyond the schema by declaring include_nested and order_by inert for query collections, but it does not explain collection_path ltree syntax or tenant_id scoping beyond what the schema states.

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 names a specific verb and resource ("Get assets in a collection") and adds return-content detail (membership metadata: position, role, added date). It does not explicitly contrast with siblings such as ListCollections or GetAssetDetails, so it stops short of full differentiation, but the scope 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Rather than saying when to use this versus an alternative, it supplies conditional behavior: for a collection_kind of "query" the results are the saved query's current matches, and include_nested/order_by are ignored. That is useful context, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources