Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dollartree_blog_article

Fetch a Dollar Tree Value Seekers Blog article by slug and article ID to get its HTML body and parent category metadata for content review or archival.

Instructions

Get a Dollar Tree Value Seekers Blog article. Returns the public DTBlogPost record for one article URL, including the HTML body and parent category metadata.

Input Schema

NameRequiredDescriptionDefault
slugYesArticle slug from the public Value Seekers Blog URL
article_idYesArticle id from the public Value Seekers Blog URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. It does disclose useful return content — an HTML body plus parent category metadata — and implies a read-only fetch of a 'public' record, but it says nothing about permissions, rate limits, whether missing IDs error or return empty, or the response envelope shape.

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?

Two sentences, zero filler, with the identification and the returned payload front-loaded. Every clause earns its place.

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 two-parameter read tool with no annotations and no output schema, the description states what is returned (HTML body, parent category metadata) well enough that an agent knows what to expect. The main residual gap is not explaining why both slug and article_id are required or what happens on a mismatch.

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%, so both parameters already document that the slug and article_id come from a public Value Seekers Blog URL, making this the baseline case. The description reinforces the single-article scoping but adds no format, relationship, or fallback detail beyond the schema.

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 gives a specific verb and resource — 'Get a Dollar Tree Value Seekers Blog article' — and names the underlying record type (DTBlogPost), which clearly separates it from the product, price, and search siblings. It does not explicitly contrast with other Dollartree tools, but the domain specificity makes selection unambiguous.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus alternatives, no prerequisite or parent-tool context (e.g., that slug/article_id must be harvested from a listing or category page first), and no exclusions. Usage is only inferable from the tool name and the 'one article URL' phrasing.

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