Skip to main content
Glama

relentless_list

Retrieve all entries from a Notion database to view existing content or search through records. Returns complete entry data for comprehensive content management.

Instructions

List all entries from a Notion database. Returns full content for all entries. Use this to see what content exists or to search through entries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
databaseYesThe database name (e.g., "blog", "docs", "leads")

Implementation Reference

  • The handler for the 'relentless_list' tool. It validates the database parameter, constructs the Relentless API endpoint, calls it using relentlessRequest, and formats the response as MCP content.
    case 'relentless_list': {
      const { database } = args as { database: string }
    
      if (!database) {
        throw new McpError(ErrorCode.InvalidParams, 'Missing required parameter: database')
      }
    
      console.error(`[${new Date().toISOString()}] Listing all from ${database}`)
    
      const endpoint = `${RELENTLESS_API_BASE}/api/v1/public/db/${database}/list`
      const result = await relentlessRequest(endpoint)
    
      return {
        content: [
          {
            type: 'text',
            text: `Found ${Array.isArray(result) ? result.length : 0} entries:\n\n${JSON.stringify(
              result,
              null,
              2
            )}`,
          },
        ],
      }
    }
  • src/index.ts:264-279 (registration)
    Registration of the 'relentless_list' tool in the MCP server's list of tools, including its name, description, and input schema.
    {
      name: 'relentless_list',
      description:
        'List all entries from a Notion database. Returns full content for all entries. Use this to see what content exists or to search through entries.',
      inputSchema: {
        type: 'object',
        properties: {
          database: {
            type: 'string',
            description: 'The database name (e.g., "blog", "docs", "leads")',
          },
        },
        required: ['database'],
      },
    },
    {
  • Input schema for the 'relentless_list' tool, defining the required 'database' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        database: {
          type: 'string',
          description: 'The database name (e.g., "blog", "docs", "leads")',
        },
      },
      required: ['database'],
    },
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 mentions the tool 'Returns full content for all entries', which hints at output behavior, but fails to address critical aspects like pagination, rate limits, permissions required, or error handling. This is inadequate for a tool that likely interacts with an external API.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded, with two sentences that directly state the tool's function and usage. There's no unnecessary verbiage, though it could be slightly more structured by separating purpose from guidelines.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'full content' entails (e.g., structured data, metadata), potential performance implications of listing all entries, or how to handle large datasets. For a tool with external dependencies and no structured output, this leaves significant gaps.

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, with the single parameter 'database' clearly documented. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. Given the high schema coverage, the baseline score of 3 is appropriate.

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 tool's purpose with a specific verb ('List') and resource ('entries from a Notion database'), and specifies the scope ('all entries', 'full content'). However, it doesn't explicitly differentiate from sibling tools like 'relentless_read' or 'relentless_index', which might have overlapping functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides implied usage guidance ('Use this to see what content exists or to search through entries'), suggesting it's for browsing or initial exploration. However, it lacks explicit when-to-use vs. when-not-to-use instructions or named alternatives among sibling tools, leaving some ambiguity.

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/PranaytheSingh/relentless-mcp'

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