Skip to main content
Glama
enesjakozh
knmurphy

Glide API MCP Server

by knmurphy
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

add_table_row

Insert a new row into a Glide app table by specifying the app ID, table ID, and column values for the row. Facilitates data management via a secure, type-safe interface.

Instructions

Add a new row to a table in a Glide app

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesID of the Glide app
tableIdYesID of the table
valuesYesColumn values for the new row

Implementation Reference

  • src/index.ts:327-341 (handler)
    Handler for the 'add_table_row' tool. Extracts appId, tableId, and values from arguments, then makes a POST request to the Glide API endpoint `/apps/{appId}/tables/{tableId}/rows` with the values to add a new row.
    case 'add_table_row': {
  const { appId, tableId, values } = request.params.arguments as {
    appId: string;
    tableId: string;
    values: Record<string, any>;
  };
  const result = await this.apiClient.makeRequest(
    'POST',
    `/apps/${appId}/tables/${tableId}/rows`,
    values
  );
  return {
    content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
  };
}
  • src/index.ts:194-216 (registration)
    Registration of the 'add_table_row' tool in the list of available tools, including its description and input schema definition.
    {
  name: 'add_table_row',
  description: 'Add a new row to 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',
      },
      values: {
        type: 'object',
        description: 'Column values for the new row',
        additionalProperties: true,
      },
    },
    required: ['appId', 'tableId', 'values'],
  },
},
  • src/index.ts:197-215 (schema)
    Input schema for the 'add_table_row' tool, defining required parameters: appId, tableId, and values object.
    inputSchema: {
  type: 'object',
  properties: {
    appId: {
      type: 'string',
      description: 'ID of the Glide app',
    },
    tableId: {
      type: 'string',
      description: 'ID of the table',
    },
    values: {
      type: 'object',
      description: 'Column values for the new row',
      additionalProperties: true,
    },
  },
  required: ['appId', 'tableId', 'values'],
},

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Add a new row' implies a write/mutation operation, it doesn't disclose important behavioral aspects like required permissions, whether the operation is idempotent, what happens on duplicate keys, error handling, or response format. The description provides minimal behavioral context beyond the basic action.

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, clear sentence that efficiently communicates the core functionality without any wasted words. It's appropriately sized for a straightforward tool and gets directly to the point with no 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?

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after the row is added, what the response contains, error conditions, or how this operation relates to other table operations. Given the complexity of a write operation with nested objects in the values parameter, more context would be helpful.

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?

With 100% schema description coverage, the input schema already documents all three parameters thoroughly. The description doesn't add any meaningful parameter semantics beyond what's in the schema - it mentions 'table' and 'Glide app' which map to parameters, but provides no additional context about parameter relationships, constraints, or usage patterns.

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 ('Add a new row') and target resource ('to a table in a Glide app'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'update_table_row' or specify what distinguishes this 'add' operation from other table operations.

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 'update_table_row' or 'get_table_rows'. There's no mention of prerequisites, error conditions, or typical use cases for adding rows versus other table operations.

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