Skip to main content
Glama
knmurphy

Glide API MCP Server

by knmurphy

get_table_rows

Retrieve rows from a specific table in a Glide app by specifying the app ID, table ID, and optional parameters like row limit and offset. Facilitates data access and management through the Glide API MCP Server.

Instructions

Get rows from a table in a Glide app

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesID of the Glide app
limitNoMaximum number of rows to return
offsetNoNumber of rows to skip
tableIdYesID of the table

Implementation Reference

  • Executes the get_table_rows tool: parses arguments, constructs API endpoint with optional limit/offset query parameters, calls Glide API via makeRequest, and returns JSON-formatted rows.
    case 'get_table_rows': {
      const { appId, tableId, limit, offset } = request.params.arguments as {
        appId: string;
        tableId: string;
        limit?: number;
        offset?: number;
      };
      const params = new URLSearchParams();
      if (limit) params.append('limit', limit.toString());
      if (offset) params.append('offset', offset.toString());
      
      const result = await this.apiClient.makeRequest(
        'GET',
        `/apps/${appId}/tables/${tableId}/rows${params.toString() ? '?' + params.toString() : ''}`
      );
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
      };
    }
  • src/index.ts:166-193 (registration)
    Registers the get_table_rows tool in the ListToolsRequestSchema handler, providing name, description, and input schema.
    {
      name: 'get_table_rows',
      description: 'Get rows from a table in a Glide app',
      inputSchema: {
        type: 'object',
        properties: {
          appId: {
            type: 'string',
            description: 'ID of the Glide app',
          },
          tableId: {
            type: 'string',
            description: 'ID of the table',
          },
          limit: {
            type: 'number',
            description: 'Maximum number of rows to return',
            minimum: 1,
          },
          offset: {
            type: 'number',
            description: 'Number of rows to skip',
            minimum: 0,
          },
        },
        required: ['appId', 'tableId'],
      },
    },
  • Input schema definition for get_table_rows tool, validating appId, tableId (required), limit, and offset parameters.
    inputSchema: {
      type: 'object',
      properties: {
        appId: {
          type: 'string',
          description: 'ID of the Glide app',
        },
        tableId: {
          type: 'string',
          description: 'ID of the table',
        },
        limit: {
          type: 'number',
          description: 'Maximum number of rows to return',
          minimum: 1,
        },
        offset: {
          type: 'number',
          description: 'Number of rows to skip',
          minimum: 0,
        },
      },
      required: ['appId', 'tableId'],
    },
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 the tool reads data ('Get rows'), implying it's likely read-only, but doesn't confirm safety, permissions, rate limits, or response format. For a data retrieval tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 that directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized for its function, earning full marks for conciseness.

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's complexity (4 parameters, no output schema, no annotations), the description is inadequate. It doesn't explain return values (e.g., row format), error conditions, or how parameters interact (e.g., limit/offset for pagination). For a data retrieval tool, this leaves too much unspecified.

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?

The input schema has 100% description coverage, so parameters are well-documented in the schema. The description adds no additional meaning beyond what the schema provides (e.g., no examples or context for appId/tableId). 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 action ('Get rows') and resource ('from a table in a Glide app'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'get_tables' (which likely lists tables rather than rows), so it misses full sibling differentiation.

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 'get_tables' or 'add_table_row'. It lacks context about prerequisites (e.g., needing app/table IDs) or exclusions, leaving the agent to infer usage from the tool name alone.

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/knmurphy/glide-api-mcp-server'

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