CamFeed Journalism Archive

Advanced journalism search

search_journalism

Read-onlyIdempotent

Use this for advanced searches of Cameron Wilson's public archive when source, content type, date filters, transcript matching, or matched snippets are needed. Query is optional; pass only filters to enumerate. Prefer search and fetch for OpenAI knowledge retrieval.

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": "search_journalism"
  }
}

Input Schema

Name	Required	Description
`to`	No	ISO date or datetime; include items published on or before this.
`from`	No	ISO date or datetime; include items published on or after this.
`kind`	No	Filter by item kind.
`limit`	No
`query`	No	Free-text search across title, summary, body, article full text, media transcripts, and quotes.
`source`	No	Filter by underlying source.

Output Schema

Name	Required	Description	Default
`count`	Yes
`items`	Yes
`title`	No
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 10, 2026

changedInput schema / properties / kind / enum

Previous value: -[
-  "news article",
-  "blog post",
-  "newsletter commentary",
-  "mastodon post",
-  "appearance",
-  "video clip"
-]New value: +[
+  "news article",
+  "blog post",
+  "newsletter commentary",
+  "mastodon post",
+  "appearance",
+  "audio",
+  "video clip"
+]

First observedJul 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already flag readOnly, idempotent, and non-destructive behavior. The description adds valuable behavioral context: 'Query is optional; pass only filters to enumerate' and mentions transcript matching and matched snippets, which are operational details beyond basic read-only semantics.

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 compact sentences: first defines purpose and triggers, second clarifies optional query and alternative tool preference. Every word earns its place; no redundancy.

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?

Given annotations, output schema, and 6 params, the description covers purpose, usage, and exclusions. It does not describe enumeration details or pagination, but limit parameter and output schema mitigate this. Slight gap is acceptable given structured metadata richness.

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 83% (5 of 6 params described; limit lacks a description). The description only groups parameters into categories ('source, content type, date filters') without adding new meaning, so it does not significantly supplement the schema.

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?

Description clearly specifies 'advanced searches of Cameron Wilson's public archive' with concrete triggers: source, content type, date filters, transcript matching, matched snippets. It also distinguishes from siblings by stating 'Prefer search and fetch for OpenAI knowledge retrieval,' making it clear this tool is for archive-specific advanced querying.

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

Usage Guidelines5/5

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

Explicitly states when to use: 'when source, content type, date filters, transcript matching, or matched snippets are needed.' It also names alternatives ('search and fetch') and clarifies optional query behavior, providing solid selection guidance.

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

All CamFeed Journalism Archive tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?