Skip to main content
Glama

relentless_read

Read a specific entry from a Notion database using its slug to retrieve full content and properties for content management.

Instructions

Read a specific entry from a Notion database by its slug. Returns the full entry with all properties and content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
databaseYesThe database name (e.g., "blog", "docs", "leads")
slugYesThe slug of the entry to read (e.g., "getting-started", "hello-world")

Implementation Reference

  • Handler for the 'relentless_read' tool. Validates input parameters (database and slug), logs the action, constructs the Relentless API endpoint for reading the specific entry, calls the relentlessRequest helper, and returns the result as formatted JSON text content.
    case 'relentless_read': {
      const { database, slug } = args as { database: string; slug: string }
    
      if (!database || !slug) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Missing required parameters: database and slug'
        )
      }
    
      console.error(`[${new Date().toISOString()}] Reading ${database}/${slug}`)
    
      const endpoint = `${RELENTLESS_API_BASE}/api/v1/public/db/${database}/read/${slug}`
      const result = await relentlessRequest(endpoint)
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      }
    }
  • Input schema defining the parameters for the relentless_read tool: database (string) and slug (string), both required.
    inputSchema: {
      type: 'object',
      properties: {
        database: {
          type: 'string',
          description: 'The database name (e.g., "blog", "docs", "leads")',
        },
        slug: {
          type: 'string',
          description:
            'The slug of the entry to read (e.g., "getting-started", "hello-world")',
        },
      },
      required: ['database', 'slug'],
    },
  • src/index.ts:244-263 (registration)
    Registration of the 'relentless_read' tool in the ListToolsRequestHandler response. Includes the tool name, description, and input schema.
    {
      name: 'relentless_read',
      description:
        'Read a specific entry from a Notion database by its slug. Returns the full entry with all properties and content.',
      inputSchema: {
        type: 'object',
        properties: {
          database: {
            type: 'string',
            description: 'The database name (e.g., "blog", "docs", "leads")',
          },
          slug: {
            type: 'string',
            description:
              'The slug of the entry to read (e.g., "getting-started", "hello-world")',
          },
        },
        required: ['database', 'slug'],
      },
    },
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the return behavior ('Returns the full entry with all properties and content'), which is helpful, but lacks details on error handling, permissions, rate limits, or whether it's read-only (implied by 'Read' but not explicit). It adds some context but could be more comprehensive.

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 two concise sentences, front-loaded with the core purpose and followed by return details. Every word earns its place, with no redundancy or fluff, making it highly efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (2 required parameters, no output schema, no annotations), the description is fairly complete: it states purpose, parameters (implied by schema), and return behavior. However, it could improve by adding more behavioral context (e.g., error cases) to fully compensate for the lack of annotations and output schema.

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 both parameters thoroughly. The description adds no additional meaning beyond what the schema provides (e.g., it doesn't explain slug format or database naming conventions). Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Read'), resource ('a specific entry from a Notion database'), and mechanism ('by its slug'), distinguishing it from siblings like relentless_list (which likely lists entries) and relentless_index (which might index content). It's precise and avoids tautology.

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 implies usage when you need a full entry by slug, but doesn't explicitly state when to use this vs. alternatives like relentless_list (for listing entries) or relentless_index (for indexing). No exclusions or prerequisites are mentioned, 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