search_blog_postsGuides and articles from the Camden Tools blog (how-tos, buying guides, brand news).
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number, starting at 1. | |
| query | No | Search text; omit for the latest posts. |
| Name | Required | Description | Default |
|---|---|---|---|
| posts | Yes | ||
| blog_url | Yes | ||
| pagination | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / posts / items / properties / excerpt / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / posts / items / properties / excerpt / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "blog_url": {
+ "type": "string"
+ },
+ "pagination": {
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "last_page": {
+ "type": "number"
+ },
+ "page": {
+ "type": "number"
+ },
+ "per_page": {
+ "type": "number"
+ },
+ "total": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "page",
+ "per_page",
+ "total",
+ "last_page"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "posts": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "categories": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "excerpt": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "id": {
+ "type": "number"
+ },
+ "published_at": {
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ },
+ "title": {
+ "type": "string"
+ },
+ "url": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "title",
+ "slug",
+ "url",
+ "excerpt",
+ "published_at",
+ "categories"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "posts",
+ "pagination",
+ "blog_url"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the content domain (how-tos, buying guides, brand news), which helps set result expectations, but says nothing about result volume, ordering, or pagination limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single tight sentence with a parenthetical that usefully enumerates content types. No filler, though it leads with the resource rather than the action, so the operation is not front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With annotations, a full schema, and an output schema, most structured context is present. The remaining gap is the missing differentiation from get_blog_post and the absence of any hint about result ordering or scope — an agent choosing between the two blog tools has to guess.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so both the page and query parameters are fully documented in the schema. The description adds no additional parameter meaning beyond what is already structured, which is the baseline for fully covered schemas.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies the resource (blog guides and articles) and its content types, but it never states the operation — the verb 'search' comes only from the tool name. It also fails to distinguish this from the sibling get_blog_post, which retrieves a single post.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this versus get_blog_post, no mention of pagination approach, and no note that omitting the query returns the latest posts (that behavior lives only in the schema). The agent must infer the search-vs-fetch split.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.