Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodrx_health_articles

Need to list GoodRx Health articles? Fetch one page by section, optionally filtered by topic, sorted by last modified date, with total counts and metadata.

Instructions

List GoodRx Health articles. Returns one page of GoodRx Health articles in a section, optionally one topic, most recently modified first: each article's path, section, topic, URL, and last-modified date, with total and total pages. Use a path with /goodrx/health-article.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, starting at 1
topicNoTopic slug from /goodrx/health-topics
sectionYesArticle section
page_sizeNoArticles per page (1-200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses ordering ("most recently modified first") and that pagination metadata is returned ("total and total pages"), and enumerates response fields. It stops short of covering auth requirements, rate limits, or what happens on invalid section/topic values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences that front-load purpose and then the pagination/return contract. It is tightly sized, with only mild redundancy between the listing statement and the return-field enumeration.

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 list tool with no annotations and no output schema, the description adequately covers ordering, pagination metadata, and returned fields. The lingering "Use a path with /goodrx/health-article" note is somewhat ambiguous and leaves slight doubt about how this relates to the singular sibling.

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 all four parameters are documented in the schema and the baseline of 3 applies. The description adds only marginal value, noting that topic is optional and that a path should be used, without explaining page vs page_size semantics or valid page_size bounds.

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 opens with a specific verb+resource ("List GoodRx Health articles") and adds scope (one page, in a section, optionally one topic) plus the returned fields. It can be told apart from the singular goodrx_health_article sibling through the listing verb, but never names that sibling explicitly, so differentiation is only implicit.

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

Usage Guidelines3/5

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

"Use a path with /goodrx/health-article" hints that this routes to the singular article tool, and "optionally one topic" implies filtering behavior, but there is no explicit when-to-use versus the related goodrx_health_article or goodrx_health_topics siblings. Usage is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools