Skip to main content
Glama
houtini-ai

YubHub MCP Server

by houtini-ai

create_feed

Create a structured job feed by monitoring careers pages to track new job postings automatically.

Instructions

Create a new job feed for monitoring career pages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFeed name (e.g., "Mercedes-AMG F1")
careersUrlYesCareers page URL to monitor
exampleJobUrlNoExample job posting URL (optional)

Implementation Reference

  • The main handler method that executes the create_feed tool logic. It accepts name, careersUrl, and optional exampleJobUrl parameters, calls the API client to create the feed, and returns a formatted success message with the feed ID.
      private async createFeed({ name, careersUrl, exampleJobUrl }: { name: string; careersUrl: string; exampleJobUrl?: string }) {
        const result = await this.apiClient.createFeed(name, careersUrl, exampleJobUrl);
    
        return {
          content: [
            {
              type: 'text',
              text: `✅ Feed created successfully!
    
    **Feed ID**: \`${result.id}\`
    **Name**: ${name}
    **Careers URL**: ${careersUrl}
    ${exampleJobUrl ? `**Example Job URL**: ${exampleJobUrl}` : ''}
    
    You can now trigger a run with: "Trigger a run for ${result.id}"`,
            },
          ],
        };
      }
  • src/index.ts:345-369 (registration)
    Tool registration defining the 'create_feed' tool with its name, description, and JSON Schema input validation specifying required fields (name, careersUrl) and optional field (exampleJobUrl) with type constraints.
    name: 'create_feed',
    description: 'Create a new job feed for monitoring career pages',
    inputSchema: {
      type: 'object',
      properties: {
        name: {
          type: 'string',
          description: 'Feed name (e.g., "Mercedes-AMG F1")',
          minLength: 1,
          maxLength: 100
        },
        careersUrl: {
          type: 'string',
          description: 'Careers page URL to monitor',
          format: 'uri'
        },
        exampleJobUrl: {
          type: 'string',
          description: 'Example job posting URL (optional)',
          format: 'uri'
        }
      },
      required: ['name', 'careersUrl'],
      additionalProperties: false
    }
  • API client helper method that makes the actual HTTP POST request to /api/feeds endpoint to create the feed, handling the API communication layer.
    async createFeed(name: string, careersUrl: string, exampleJobUrl?: string): Promise<{ id: string; message: string }> {
      return this.request('/api/feeds', {
        method: 'POST',
        body: JSON.stringify({ name, careersUrl, exampleJobUrl }),
      });
    }
  • TypeScript interface defining the Feed data structure including id, name, careers_url, example_job_url, is_active, timestamps, and scheduler fields.
    export interface Feed {
      id: string;
      name: string;
      user_id: number;
      careers_url: string;
      example_job_url: string | null;
      is_active: number;
      last_run_at: number | null;
      created_at: number;
      tag: string | null;
      updated_at: number;
      // Scheduler fields
      auto_run_enabled?: number;
      run_interval_days?: number;
      next_run_at?: number | null;
    }
  • src/index.ts:662-663 (registration)
    Switch case routing that maps the 'create_feed' tool name to its handler method, part of the tool execution dispatcher.
    case 'create_feed':
      return await this.createFeed(args as any);
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like permissions needed, whether creation is idempotent, rate limits, or what happens on success/failure. For a creation tool with zero annotation coverage, this is inadequate.

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 that directly states the tool's purpose without any fluff or redundancy. It's appropriately sized and front-loaded.

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?

For a creation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what a 'job feed' entails, what monitoring involves, or what the tool returns. Given the complexity implied by sibling tools and lack of structured data, more context is needed.

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 parameters. The description doesn't add any meaning beyond what's in the schema (e.g., it doesn't explain relationships between parameters or usage nuances). Baseline 3 is appropriate when 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 action ('Create') and resource ('new job feed for monitoring career pages'), providing a specific purpose. However, it doesn't explicitly differentiate from sibling tools like 'update_feed' or 'list_feeds', which would require a 5.

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 like 'update_feed' or 'list_feeds', nor does it mention prerequisites or exclusions. It only states what the tool does, not when it's appropriate.

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/houtini-ai/yubhub'

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