Skip to main content
Glama

list_articles

Read-only

List published articles on hellobooks.ai — head-to-head compare pages and curated flagship blog posts. Filter by country, tag or free-text query. Use this when a user asks "do you have a blog/article about X?".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoSingle tag to filter on (case-insensitive substring match against the article tag list). e.g. "gst", "1099", "tally".
limitNoMax articles to return (default 20).
queryNoFree-text query — substring-matched against the title, excerpt and tags of each article. e.g. "QuickBooks alternative" or "audit trail".
countryNoISO country code or "global". Returns articles whose countryRelevance matches OR is "global". Omit to return everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "IN",
      -  "AU",
      -  "US",
      -  "CA",
      -  "GB",
      -  "AE",
      -  "SG",
      -  "NZ",
      -  "global"
      -]New value: +[
      +  "IN",
      +  "US",
      +  "GB",
      +  "AU",
      +  "AE",
      +  "CA",
      +  "SG",
      +  "NZ",
      +  "HK",
      +  "DE",
      +  "FR",
      +  "NL",
      +  "ES",
      +  "IT",
      +  "JP",
      +  "KR",
      +  "SA",
      +  "IE",
      +  "ZA",
      +  "MY",
      +  "PH",
      +  "NG",
      +  "KE",
      +  "ID",
      +  "TH",
      +  "VN",
      +  "PK",
      +  "BD",
      +  "BR",
      +  "MX",
      +  "AR",
      +  "CL",
      +  "CO",
      +  "SE",
      +  "NO",
      +  "DK",
      +  "FI",
      +  "BE",
      +  "AT",
      +  "CH",
      +  "PL",
      +  "PT",
      +  "CZ",
      +  "RO",
      +  "HU",
      +  "GR",
      +  "TR",
      +  "UA",
      +  "IL",
      +  "EG",
      +  "BG",
      +  "HR",
      +  "SI",
      +  "SK",
      +  "LT",
      +  "LV",
      +  "EE",
      +  "RS",
      +  "MA",
      +  "QA",
      +  "KW",
      +  "JO",
      +  "OM",
      +  "BH",
      +  "TN",
      +  "DZ",
      +  "GH",
      +  "TZ",
      +  "UG",
      +  "ET",
      +  "ZM",
      +  "ZW",
      +  "RW",
      +  "SN",
      +  "LK",
      +  "NP",
      +  "MM",
      +  "KH",
      +  "LA",
      +  "PE",
      +  "EC",
      +  "BO",
      +  "PY",
      +  "UY",
      +  "CR",
      +  "PA",
      +  "GT",
      +  "DO",
      +  "KZ",
      +  "UZ",
      +  "BY",
      +  "MD",
      +  "BA",
      +  "MK",
      +  "AL",
      +  "LB",
      +  "IQ",
      +  "TT",
      +  "MO",
      +  "BN",
      +  "CY",
      +  "MT",
      +  "LU",
      +  "IS",
      +  "ME",
      +  "GE",
      +  "AM",
      +  "AZ",
      +  "TM",
      +  "TJ",
      +  "KG",
      +  "MN",
      +  "CI",
      +  "CM",
      +  "TG",
      +  "BJ",
      +  "BF",
      +  "ML",
      +  "SL",
      +  "LR",
      +  "GN",
      +  "MR",
      +  "NE",
      +  "TD",
      +  "CD",
      +  "CG",
      +  "GA",
      +  "MW",
      +  "MZ",
      +  "NA",
      +  "BW",
      +  "LS",
      +  "SZ",
      +  "MG",
      +  "AO",
      +  "MU",
      +  "SC",
      +  "CV",
      +  "HN",
      +  "SV",
      +  "NI",
      +  "JM",
      +  "BB",
      +  "GY",
      +  "SR",
      +  "FJ",
      +  "PG",
      +  "HT",
      +  "BS",
      +  "VE",
      +  "IR",
      +  "AF",
      +  "SY",
      +  "YE",
      +  "LY",
      +  "SD",
      +  "SO",
      +  "CU",
      +  "KP",
      +  "TW",
      +  "PS",
      +  "ER",
      +  "DJ",
      +  "SS",
      +  "CF",
      +  "GQ",
      +  "BI",
      +  "KM",
      +  "ST",
      +  "GW",
      +  "EH",
      +  "WS",
      +  "TO",
      +  "VU",
      +  "SB",
      +  "KI",
      +  "TV",
      +  "NR",
      +  "PW",
      +  "FM",
      +  "MH",
      +  "AG",
      +  "LC",
      +  "VC",
      +  "KN",
      +  "DM",
      +  "GD",
      +  "global"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful context that only 'published' articles are returned and that the corpus spans two article types, but it says nothing about result ordering, pagination behavior despite a limit parameter, or what an empty result means.

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?

Three short sentences, front-loaded with the resource and content scope, then filters, then the invocation trigger. Every sentence earns its place; minor redundancy between 'head-to-head compare pages' and the query example, but nothing wasteful.

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 four-parameter, all-optional, read-only listing tool with full schema coverage and no output schema, the description covers purpose, content scope, filters and a trigger example. Only return-shape/ordering and pagination hints are absent, which is a small gap given the absence of an 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 coverage is 100% with rich per-parameter descriptions, including the country/global matching rule and the tag and query match targets. The description only restates the three filter dimensions and omits limit entirely, so it adds essentially no meaning beyond the schema — the baseline 3 is appropriate.

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?

States a specific verb and resource ('List published articles on hellobooks.ai') and scopes the content precisely to 'head-to-head compare pages and curated flagship blog posts', which clearly distinguishes it from sibling listers such as list_videos, list_features or feature_search. An agent knows exactly what corpus this tool searches without opening the schema.

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?

Gives an explicit trigger with a user-intent example: 'Use this when a user asks "do you have a blog/article about X?"'. That is actionable guidance for the main use case, though it does not say when NOT to use it or name a sibling (e.g. feature_search) for product-capability lookups.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources