Skip to content

fix(dashboard): MCP ingestion 422 errors — wrong parameter name#4

Merged
jeremylongshore merged 1 commit intomainfrom
fix/ingestion-mcp-parameter-mismatch
Feb 13, 2026
Merged

fix(dashboard): MCP ingestion 422 errors — wrong parameter name#4
jeremylongshore merged 1 commit intomainfrom
fix/ingestion-mcp-parameter-mismatch

Conversation

@jeremylongshore
Copy link
Collaborator

@jeremylongshore jeremylongshore commented Feb 13, 2026

Summary

  • Dashboard "Run Ingestion" button was sending {"feed_id": "hackernews"} to the MCP service
  • MCP FetchRSSFeedRequest schema requires feed_url (a real URL), not feed_id
  • Pydantic validation rejected every request with a 422 Unprocessable Entity error
  • Also fixed the curl example in CLAUDE.md that had the same wrong parameter

Root cause: Parameter mismatch introduced in commit 1911c70

Test plan

  • Click "Run Ingestion" on dashboard — should succeed and show article count
  • Verify no 422 errors in Cloud Run logs
  • Verify curl example in CLAUDE.md works: curl -X POST .../mcp/tools/fetch_rss_feed -H "Content-Type: application/json" -d '{"feed_url": "https://news.ycombinator.com/rss", "max_items": 10}'

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated RSS feed ingestion configuration to use direct URLs instead of feed identifiers, and added configurable parameters for maximum items and time window settings.

…oint

Dashboard was sending {feed_id: "hackernews"} but the MCP service expects
{feed_url: "https://..."} — causing 422 validation errors on every ingestion.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@gemini-code-assist
Copy link

Summary of Changes

Hello @jeremylongshore, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses and resolves a critical issue where the dashboard's RSS feed ingestion and a related documentation example were failing due to an incorrect parameter name. By standardizing the parameter from feed_id to feed_url and including additional necessary fields, the system can now successfully process RSS feed requests, eliminating previous 422 errors and improving overall reliability.

Highlights

  • Parameter Correction: The feed_id parameter, incorrectly used in the dashboard's 'Run Ingestion' button and a curl example, has been replaced with the correct feed_url parameter, resolving 422 Unprocessable Entity errors.
  • Dashboard Functionality: The dashboard's RSS feed ingestion now correctly sends feed_url, time_window_hours, and max_items to the MCP service, allowing successful ingestion.
  • Documentation Update: The CLAUDE.md documentation has been updated to reflect the correct curl command for fetching RSS feeds, ensuring consistency and accuracy.
Changelog
  • CLAUDE.md
    • Updated the curl example for fetch_rss_feed to use feed_url instead of feed_id and included max_items.
  • dashboard/src/pages/Dashboard.tsx
    • Modified the fetch request body for the fetch_rss_feed endpoint to correctly pass feed_url, time_window_hours, and max_items.
Activity
  • The pull request was generated with Claude Code, indicating an AI-assisted development process.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai
Copy link

coderabbitai bot commented Feb 13, 2026

📝 Walkthrough

Walkthrough

The RSS feed ingestion configuration is updated to use URL-based sources instead of feed identifiers. The feed URL is changed to "https://news.ycombinator.com/rss" across multiple files, with additional parameters for limiting items and time windows added to the request payload.

Changes

Cohort / File(s) Summary
RSS Feed Configuration
CLAUDE.md, dashboard/src/pages/Dashboard.tsx
Changed RSS feed source from feed_id-based identifier ("hackernews") to explicit URL ("https://news.ycombinator.com/rss"), with added max_items and time_window_hours parameters for request payloads.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A rabbit hopped with glee today,
Feed IDs traded for URLs at play,
Now Hacker News flows with thirty or ten,
Time windows set—refresh again and again! 📰

🚥 Pre-merge checks | ✅ 3 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: fixing MCP ingestion 422 errors by correcting the parameter name from feed_id to feed_url, which directly matches the changeset.
Description check ✅ Passed The description covers all required template sections: What's this PR do (summary), Why (root cause and problem), Testing (test plan with checkboxes), and includes additional context about the parameter mismatch.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into main

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/ingestion-mcp-parameter-mismatch

No actionable comments were generated in the recent review. 🎉


Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly resolves a 422 Unprocessable Entity error that occurred when triggering ingestion from the dashboard. The issue was due to an incorrect parameter name being sent to the MCP service. The fix involves changing feed_id to feed_url in the request payload within dashboard/src/pages/Dashboard.tsx and also updating an incorrect curl example in CLAUDE.md. The changes are accurate and effectively address the bug. I have provided one suggestion to improve code maintainability by extracting hardcoded values into constants.

method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ feed_id: 'hackernews' })
body: JSON.stringify({ feed_url: 'https://news.ycombinator.com/rss', time_window_hours: 24, max_items: 50 })

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

While this change correctly fixes the ingestion error, it introduces hardcoded values for the feed URL and ingestion parameters. To improve maintainability and readability, it's better to define these as constants at the top of the file, similar to how MCP_URL is defined.

For example, you could add these constants:

const HACKERNEWS_RSS_URL = 'https://news.ycombinator.com/rss';
const INGESTION_TIME_WINDOW_HOURS = 24;
const INGESTION_MAX_ITEMS = 50;

Then, you can use them in the fetch call as suggested.

Suggested change
body: JSON.stringify({ feed_url: 'https://news.ycombinator.com/rss', time_window_hours: 24, max_items: 50 })
body: JSON.stringify({ feed_url: HACKERNEWS_RSS_URL, time_window_hours: INGESTION_TIME_WINDOW_HOURS, max_items: INGESTION_MAX_ITEMS })

@jeremylongshore jeremylongshore merged commit 0d5a7c8 into main Feb 13, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant