Skip to main content
Glama
houtini-ai

YubHub MCP Server

by houtini-ai

disable_feed_auto_run

Disable automatic feed execution to gain manual control over when job feed updates run, preventing unwanted automated refreshes.

Instructions

Disable automatic runs for a feed. The feed will require manual triggering after this. Use this when you want full control over when a feed runs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedIdYesFeed ID to disable auto-run for

Implementation Reference

  • The main handler function that disables auto-run for a feed by calling apiClient.updateFeedSchedule with enabled=false
      private async disableFeedAutoRun({ feedId }: { feedId: string }) {
        await this.apiClient.updateFeedSchedule(feedId, false);
    
        return {
          content: [
            {
              type: 'text',
              text: `⚪ Auto-run disabled
    
    **Feed ID**: \`${feedId}\`
    
    This feed will no longer run automatically. Use "Trigger Feed Run" to run it manually.`,
            },
          ],
        };
      }
  • Tool registration including name, description, and input schema defining the feedId parameter
    {
      name: 'disable_feed_auto_run',
      description: 'Disable automatic runs for a feed. The feed will require manual triggering after this. Use this when you want full control over when a feed runs.',
      inputSchema: {
        type: 'object',
        properties: {
          feedId: {
            type: 'string',
            description: 'Feed ID to disable auto-run for'
          }
        },
        required: ['feedId'],
        additionalProperties: false
      }
    },
  • src/index.ts:692-694 (registration)
    Switch case that routes tool calls to the disableFeedAutoRun handler
    case 'disable_feed_auto_run':
      return await this.disableFeedAutoRun(args as any);
  • API client helper method that makes the actual PATCH request to update feed schedule settings
    async updateFeedSchedule(
      feedId: string,
      enabled: boolean,
      intervalDays: number = 7
    ): Promise<{ message: string; feedId: string; intervalDays: number; nextRunAt: string | null }> {
      return this.request(`/api/feeds/${feedId}/schedule`, {
        method: 'PATCH',
        body: JSON.stringify({ enabled, intervalDays }),
      });
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the behavioral effect ('The feed will require manual triggering after this'), which is useful context. However, it lacks details on permissions, reversibility (e.g., via 'enable_feed_auto_run'), or error conditions, leaving gaps for a mutation tool.

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 sentences, front-loaded with the core purpose and followed by usage guidance. Every sentence adds value without redundancy, making it efficient and well-structured.

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 mutation tool with no annotations and no output schema, the description is reasonably complete—it explains the action, outcome, and usage context. However, it could improve by mentioning related tools (e.g., 'enable_feed_auto_run' for reversal) or potential side effects, given the complexity of disabling automation.

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%, with the single parameter 'feedId' well-documented in the schema. The description adds no additional parameter details beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

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 ('Disable automatic runs') and the resource ('for a feed'), distinguishing it from sibling tools like 'enable_feed_auto_run' and 'trigger_feed_run'. It precisely defines the tool's function without being tautological.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('Use this when you want full control over when a feed runs') and implies an alternative (manual triggering via 'trigger_feed_run'). It provides clear context for its application versus other feed management tools.

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