Skip to main content
Glama
MustafaPatharia

ProofHub MCP Server

proofhub_parse_url

Parse a ProofHub task URL to extract project, list, and task IDs. Required as first step before using other ProofHub tools.

Instructions

Parse a ProofHub task URL and return the project ID, list ID, and task ID embedded in it. Use this as the first step before calling other ProofHub tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull ProofHub task URL, e.g. https://kpi.proofhub.com/bappswift/#app/todos/project-7189443252/list-270280503800/task-514774338823

Implementation Reference

  • Handler for proofhub_parse_url tool. Calls parseProofHubUrl() to extract project/list/task IDs from a ProofHub URL, then returns them as JSON. Throws if no task ID is found.
    // ── proofhub_parse_url ───────────────────────────────────────────────
    if (name === 'proofhub_parse_url') {
      const ids = parseProofHubUrl(args.url);
      if (!ids.taskId) throw new Error('Could not find a task ID in the URL.');
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(ids, null, 2),
        }],
      };
    }
  • Tool schema registration for proofhub_parse_url, defining its name, description, and inputSchema (requires a 'url' string property).
    {
      name: 'proofhub_parse_url',
      description:
        'Parse a ProofHub task URL and return the project ID, list ID, and task ID embedded in it. ' +
        'Use this as the first step before calling other ProofHub tools.',
      inputSchema: {
        type: 'object',
        properties: {
          url: { type: 'string', description: 'Full ProofHub task URL, e.g. https://kpi.proofhub.com/bappswift/#app/todos/project-7189443252/list-270280503800/task-514774338823' },
        },
        required: ['url'],
      },
    },
  • index.js:102-187 (registration)
    Tool is registered in the ListToolsRequestSchema handler as part of the tools array returned by the MCP server.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        {
          name: 'proofhub_parse_url',
          description:
            'Parse a ProofHub task URL and return the project ID, list ID, and task ID embedded in it. ' +
            'Use this as the first step before calling other ProofHub tools.',
          inputSchema: {
            type: 'object',
            properties: {
              url: { type: 'string', description: 'Full ProofHub task URL, e.g. https://kpi.proofhub.com/bappswift/#app/todos/project-7189443252/list-270280503800/task-514774338823' },
            },
            required: ['url'],
          },
        },
        {
          name: 'proofhub_get_task',
          description: 'Fetch full task details (title, description, stage, custom fields, assignees) from ProofHub.',
          inputSchema: {
            type: 'object',
            properties: {
              project_id: { type: 'string' },
              list_id:    { type: 'string' },
              task_id:    { type: 'string' },
            },
            required: ['project_id', 'list_id', 'task_id'],
          },
        },
        {
          name: 'proofhub_get_comments',
          description: 'Fetch all comments on a ProofHub task, including their full text.',
          inputSchema: {
            type: 'object',
            properties: {
              project_id: { type: 'string' },
              list_id:    { type: 'string' },
              task_id:    { type: 'string' },
            },
            required: ['project_id', 'list_id', 'task_id'],
          },
        },
        {
          name: 'proofhub_get_task_with_bug_links',
          description:
            'One-shot tool: given a ProofHub task URL (or IDs), fetches the task description AND all comments, ' +
            'then extracts any bug-tracker links (Jira, Linear, GitHub Issues, GitLab, YouTrack, ClickUp, Asana, etc.) ' +
            'found in any of those texts. Returns the task data plus a deduplicated list of bug links.',
          inputSchema: {
            type: 'object',
            properties: {
              url:        { type: 'string', description: 'Full ProofHub task URL (preferred). If supplied, project_id/list_id/task_id are ignored.' },
              project_id: { type: 'string' },
              list_id:    { type: 'string' },
              task_id:    { type: 'string' },
            },
          },
        },
        {
          name: 'proofhub_create_comment',
          description: 'Post a new comment on a ProofHub task.',
          inputSchema: {
            type: 'object',
            properties: {
              project_id:  { type: 'string' },
              list_id:     { type: 'string' },
              task_id:     { type: 'string' },
              description: { type: 'string', description: 'Comment text (plain text or HTML).' },
            },
            required: ['project_id', 'list_id', 'task_id', 'description'],
          },
        },
        {
          name: 'proofhub_get_task_history',
          description: 'Fetch the activity history of a ProofHub task (stage changes, edits, etc.).',
          inputSchema: {
            type: 'object',
            properties: {
              project_id: { type: 'string' },
              list_id:    { type: 'string' },
              task_id:    { type: 'string' },
            },
            required: ['project_id', 'list_id', 'task_id'],
          },
        },
      ],
    }));
  • Helper function parseProofHubUrl() that uses regex to extract project-XXX, list-XXX, and task-XXX IDs from a ProofHub URL.
    function parseProofHubUrl(url) {
      const projectMatch = url.match(/project-(\d+)/);
      const listMatch    = url.match(/list-(\d+)/);
      const taskMatch    = url.match(/task-(\d+)/);
      return {
        projectId: projectMatch?.[1] || null,
        listId:    listMatch?.[1]    || null,
        taskId:    taskMatch?.[1]    || null,
      };
    }
Behavior4/5

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

With no annotations, the description fully explains the behavior: parsing a URL and extracting three IDs. It does not cover error handling for malformed URLs, but for a low-risk transformation the disclosure is adequate.

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 brief (two sentences) and front-loaded with the action. Every sentence adds essential information: what it does and when to use it. No unnecessary words.

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 simplicity (one parameter, no output schema), the description adequately covers the return values (three IDs) and usage context. It could explicitly state the output format, but the implied return is sufficient for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already describes the 'url' parameter fully (100% coverage with example). The description adds value by explaining what IDs are extracted from the URL, going beyond the schema's structural description to convey the tool's purpose.

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 tool's action: 'Parse a ProofHub task URL and return the project ID, list ID, and task ID.' This is a specific verb-resource pair that distinguishes it from sibling tools that create, get, or fetch different entities.

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

Usage Guidelines4/5

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

The description explicitly advises 'Use this as the first step before calling other ProofHub tools,' providing clear sequential context. It does not mention alternatives or when not to use, but the guidance is sufficiently direct for a simple preprocessing tool.

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/MustafaPatharia/proofhub-mcp'

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