Skip to main content
Glama
enesjakozh
knmurphy

Glide API MCP Server

by knmurphy
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

update_table_row

Modify specific row data in a Glide app table by providing the app ID, table ID, row ID, and updated column values through the Glide API MCP Server.

Instructions

Update an existing row in a table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesID of the Glide app
rowIdYesID of the row to update
tableIdYesID of the table
valuesYesNew column values for the row

Implementation Reference

  • src/index.ts:343-358 (handler)
    The handler function for the 'update_table_row' tool. It extracts parameters from the request, makes a POST request to the Glide API to update the specified row in the table, and returns the JSON response.
    case 'update_table_row': {
  const { appId, tableId, rowId, values } = request.params.arguments as {
    appId: string;
    tableId: string;
    rowId: string;
    values: Record<string, any>;
  };
  const result = await this.apiClient.makeRequest(
    'POST',
    `/apps/${appId}/tables/${tableId}/rows/${rowId}`,
    values
  );
  return {
    content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
  };
}
  • src/index.ts:218-243 (registration)
    Registration of the 'update_table_row' tool in the listTools response, including its name, description, and detailed input schema definition.
      name: 'update_table_row',
  description: 'Update an existing row in a table',
  inputSchema: {
    type: 'object',
    properties: {
      appId: {
        type: 'string',
        description: 'ID of the Glide app',
      },
      tableId: {
        type: 'string',
        description: 'ID of the table',
      },
      rowId: {
        type: 'string',
        description: 'ID of the row to update',
      },
      values: {
        type: 'object',
        description: 'New column values for the row',
        additionalProperties: true,
      },
    },
    required: ['appId', 'tableId', 'rowId', 'values'],
  },
},
  • src/index.ts:220-242 (schema)
    Input schema definition for the 'update_table_row' tool, specifying parameters appId, tableId, rowId, and values object.
    inputSchema: {
  type: 'object',
  properties: {
    appId: {
      type: 'string',
      description: 'ID of the Glide app',
    },
    tableId: {
      type: 'string',
      description: 'ID of the table',
    },
    rowId: {
      type: 'string',
      description: 'ID of the row to update',
    },
    values: {
      type: 'object',
      description: 'New column values for the row',
      additionalProperties: true,
    },
  },
  required: ['appId', 'tableId', 'rowId', 'values'],
},

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Update' implying mutation but lacks details on permissions, whether changes are reversible, error handling, or response format. For a mutation tool with zero annotation coverage, this is a significant gap in behavioral disclosure.

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 waste. It's appropriately sized and front-loaded, directly stating the core action 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 this is a mutation tool with no annotations, no output schema, and incomplete behavioral transparency, the description is inadequate. It should cover more about the update operation's effects, error cases, or response expectations to be complete for agent 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 schema fully documents all 4 parameters. The description adds no additional meaning beyond implying that 'values' maps to column updates, which is already clear from 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 ('Update') and resource ('an existing row in a table'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'add_table_row' (create vs. update) or 'get_table_rows' (read vs. write), which prevents a perfect score.

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. It doesn't mention prerequisites (e.g., needing row IDs from 'get_table_rows'), exclusions, or comparisons to siblings like 'add_table_row' for new rows or 'get_table_rows' for reading data.

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