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 / (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, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context about the content types (how-tos, buying guides, brand news) but does not disclose behavior such as pagination, ordering, or how query omission behaves beyond what the schema already states.
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?
The description is a single concise sentence with no filler. It front-loads the resource and scope, though it could be slightly more informative without becoming verbose.
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?
For a simple read-only search tool with full schema coverage and an output schema, the description is mostly adequate. The main gap is the lack of usage guidance distinguishing it from get_blog_post, which an agent would need to choose correctly among siblings.
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%, with both page and query already documented in the schema. The description adds no additional parameter-level meaning, so the baseline of 3 is appropriate.
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 title provides the verb 'Search' and the description identifies the resource as 'Guides and articles from the Camden Tools blog,' which is specific enough to distinguish it from the singular get_blog_post sibling. It could be stronger by explicitly stating it returns a list of matching posts, but the scope and content types are clear.
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?
No guidance is given about when to use this tool versus alternatives such as get_blog_post or search_products. The description implies it is for blog content, but it does not state exclusions, prerequisites, or when a sibling would be more appropriate.
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.