Skip to main content
Glama

getItems

Retrieve items from a specific collection in Directus using the MCP Server by providing API details, collection name, and optional query parameters for filtering, sorting, or limiting results.

Instructions

Get items from a collection in Directus

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionYesCollection name
queryNoQuery parameters like filter, sort, limit, etc. (optional)
tokenNoAuthentication token (default from config)
urlNoDirectus API URL (default from config)

Implementation Reference

  • The handler logic for the 'getItems' tool. It retrieves authentication token, collection name, and optional query parameters from inputs, performs a GET request to the Directus API endpoint `/items/{collection}` using axios, and returns the response data as JSON.
    case "getItems": {
      const token = toolArgs.token || CONFIG.DIRECTUS_ACCESS_TOKEN;
      const collection = toolArgs.collection as string;
      const query = toolArgs.query as Record<string, any> | undefined;
      
      const response = await axios.get(
        `${url}/items/${collection}`, 
        { 
          headers: buildHeaders(token),
          params: query
        }
      );
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2)
          }
        ]
      };
    }
  • Input schema for the 'getItems' tool, defining properties for url, token, collection (required), and optional query object.
    inputSchema: {
      type: "object",
      properties: {
        url: { 
          type: "string", 
          description: "Directus API URL (default from config)"
        },
        token: { 
          type: "string", 
          description: "Authentication token (default from config)"
        },
        collection: { 
          type: "string", 
          description: "Collection name" 
        },
        query: { 
          type: "object", 
          description: "Query parameters like filter, sort, limit, etc. (optional)"
        }
      },
      required: ["collection"]
    }
  • index.ts:88-112 (registration)
    Registration of the 'getItems' tool in the listTools response, including name, description, and input schema.
    {
      name: "getItems",
      description: "Get items from a collection in Directus",
      inputSchema: {
        type: "object",
        properties: {
          url: { 
            type: "string", 
            description: "Directus API URL (default from config)"
          },
          token: { 
            type: "string", 
            description: "Authentication token (default from config)"
          },
          collection: { 
            type: "string", 
            description: "Collection name" 
          },
          query: { 
            type: "object", 
            description: "Query parameters like filter, sort, limit, etc. (optional)"
          }
        },
        required: ["collection"]
      }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'Get items' but doesn't explain whether this is a read-only operation, if it requires authentication, what happens on errors, or if there are rate limits. For a tool with 4 parameters and no annotation coverage, this leaves significant behavioral gaps.

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?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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?

Given the tool has 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain the return format (e.g., list of items, pagination), error conditions, or authentication requirements, leaving the agent with insufficient context for reliable use.

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 input schema already documents all parameters well. The description adds no additional parameter semantics beyond implying 'collection' is the target and 'items' are retrieved, which is redundant with the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 the verb 'Get' and the resource 'items from a collection in Directus', making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'getItem' (singular), which appears to retrieve a single item rather than multiple items from a collection.

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?

The description provides no guidance on when to use this tool versus alternatives like 'getItem' (for single items) or 'getCollections' (for collection metadata). It mentions the context 'in Directus' but offers no explicit when/when-not instructions or comparisons to sibling tools.

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

Related 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/pixelsock/directus-mcp'

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