Skip to main content
Glama
andrewlwn77
by andrewlwn77

get_view_data

Retrieve records from a specific NocoDB view by providing base ID, table name, and view ID. Supports pagination with limit and offset parameters for efficient data access.

Instructions

Get records from a specific view

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idYesThe ID of the base/project
table_nameYesThe name of the table
view_idYesThe ID of the view
limitNoNumber of records to return
offsetNoNumber of records to skip

Implementation Reference

  • The handler function that implements the core logic of the 'get_view_data' tool, fetching records from a specific view using the NocoDBClient's listRecords method with viewId, limit, and offset parameters.
    handler: async (
      client: NocoDBClient,
      args: {
        base_id: string;
        table_name: string;
        view_id: string;
        limit?: number;
        offset?: number;
      },
    ) => {
      const result = await client.listRecords(args.base_id, args.table_name, {
        viewId: args.view_id,
        limit: args.limit,
        offset: args.offset,
      });
      return {
        records: result.list,
        pageInfo: result.pageInfo,
        count: result.list.length,
        view_id: args.view_id,
      };
    },
  • Input schema defining the parameters for the 'get_view_data' tool: base_id, table_name, view_id (required), and optional limit and offset.
    inputSchema: {
      type: "object",
      properties: {
        base_id: {
          type: "string",
          description: "The ID of the base/project",
        },
        table_name: {
          type: "string",
          description: "The name of the table",
        },
        view_id: {
          type: "string",
          description: "The ID of the view",
        },
        limit: {
          type: "number",
          description: "Number of records to return",
        },
        offset: {
          type: "number",
          description: "Number of records to skip",
        },
      },
      required: ["base_id", "table_name", "view_id"],
    },
  • src/index.ts:55-62 (registration)
    Registers the 'get_view_data' tool by including the viewTools array (containing it) in the allTools array, which is used for listing and calling tools in the MCP server handlers.
    const allTools = [
      ...databaseTools,
      ...tableTools,
      ...recordTools,
      ...viewTools,
      ...queryTools,
      ...attachmentTools,
    ];
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get records' implies a read operation, but it doesn't specify permissions needed, rate limits, pagination behavior (beyond schema parameters), error conditions, or what 'specific view' entails (e.g., filtered/sorted data). For a tool with 5 parameters and no annotations, this is a significant gap in behavioral context.

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—'Get records from a specific view' is front-loaded and appropriately sized for its purpose. Every word earns its place, making it highly concise and well-structured.

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 complexity (5 parameters, no output schema, no annotations, and multiple sibling tools for similar functions), the description is incomplete. It lacks context on behavior, usage guidelines, and output expectations, making it inadequate for an AI agent to fully understand when and how to invoke this tool correctly.

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 already documents all 5 parameters with clear descriptions. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't explain relationships between parameters like how 'view_id' relates to 'table_name' or typical use cases for 'limit' and 'offset'). 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 'Get records from a specific view' clearly states the action (get) and resource (records from a specific view), which is a specific verb+resource combination. However, it doesn't distinguish itself from sibling tools like 'get_record', 'list_records', 'query', or 'search_records' that also retrieve records, 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. It doesn't mention prerequisites, context, or exclusions, and with multiple sibling tools for retrieving records (e.g., 'get_record', 'list_records', 'query', 'search_records'), there's no indication of when this specific view-based retrieval is preferred.

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

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/andrewlwn77/nocodb-mcp'

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