Skip to main content
Glama
houtini-ai

YubHub MCP Server

by houtini-ai

enable_feed_auto_run

Schedule automatic weekly runs for job feeds to maintain updated content without manual intervention, using configurable intervals.

Instructions

Enable automatic weekly runs for a feed. The scheduler worker runs hourly and will automatically trigger this feed at the configured interval (default: 7 days for weekly runs). Great for keeping job feeds updated without manual intervention.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedIdYesFeed ID to enable auto-run for
intervalDaysNoRun interval in days (default: 7 for weekly, max: 168 for ~monthly)

Implementation Reference

  • Handler function that enables automatic runs for a feed by calling apiClient.updateFeedSchedule with the feedId, enabled flag (true), and intervalDays. Returns a success message with the feed ID, interval, and next run time.
      private async enableFeedAutoRun({ feedId, intervalDays = 7 }: { feedId: string; intervalDays?: number }) {
        const result = await this.apiClient.updateFeedSchedule(feedId, true, intervalDays);
    
        const nextRun = result.nextRunAt
          ? new Date(result.nextRunAt).toLocaleString()
          : 'Not scheduled';
    
        return {
          content: [
            {
              type: 'text',
              text: `✅ Auto-run enabled successfully!
    
    **Feed ID**: \`${feedId}\`
    **Interval**: Every ${intervalDays} day${intervalDays !== 1 ? 's' : ''}
    **Next Run**: ${nextRun}
    
    This feed will now trigger automatically every ${intervalDays} days. The scheduler runs hourly and will pick up this feed when it's due.`,
            },
          ],
        };
      }
  • src/index.ts:501-522 (registration)
    Tool registration defining the tool name 'enable_feed_auto_run', its description, and input schema with feedId (required string) and intervalDays (optional integer, default 7, range 1-168).
    {
      name: 'enable_feed_auto_run',
      description: 'Enable automatic weekly runs for a feed. The scheduler worker runs hourly and will automatically trigger this feed at the configured interval (default: 7 days for weekly runs). Great for keeping job feeds updated without manual intervention.',
      inputSchema: {
        type: 'object',
        properties: {
          feedId: {
            type: 'string',
            description: 'Feed ID to enable auto-run for'
          },
          intervalDays: {
            type: 'integer',
            description: 'Run interval in days (default: 7 for weekly, max: 168 for ~monthly)',
            minimum: 1,
            maximum: 168,
            default: 7
          }
        },
        required: ['feedId'],
        additionalProperties: false
      }
    },
  • Switch case dispatcher that routes 'enable_feed_auto_run' tool calls to the enableFeedAutoRun handler method.
    case 'enable_feed_auto_run':
      return await this.enableFeedAutoRun(args as any);
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 key behavioral traits: the tool enables automatic scheduling, mentions the scheduler runs hourly, specifies the default interval (7 days), and describes the purpose ('keeping job feeds updated without manual intervention'). However, it doesn't cover potential side effects, error conditions, or what happens if the feed doesn't exist.

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 efficiently structured in two sentences: the first states the core purpose and key behavioral details (scheduler frequency, default interval), and the second provides usage context. Every sentence adds value with zero wasted words, making it 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?

For a tool with 2 parameters, 100% schema coverage, and no output schema, the description provides adequate context: it explains what the tool does, why to use it, and key behavioral aspects. However, it doesn't mention what the tool returns (success/failure indicators) or error handling, which would be helpful given the lack of 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 fully documents both parameters. The description adds minimal value beyond the schema: it mentions 'weekly runs' and 'configured interval' which aligns with the schema's 'intervalDays' parameter, but doesn't provide additional semantic context or usage examples. The baseline of 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.

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 ('Enable automatic weekly runs') on a specific resource ('for a feed'), distinguishing it from sibling tools like 'disable_feed_auto_run' (opposite action) and 'trigger_feed_run' (manual vs. automatic). The verb 'enable' is precise and the resource 'feed' is unambiguous.

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 provides clear context about when to use this tool ('Great for keeping job feeds updated without manual intervention') and mentions the scheduler's hourly operation and default interval. However, it doesn't explicitly state when NOT to use it or compare it to alternatives like 'trigger_feed_run' for one-time execution.

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