note.com MCP Server

search-magazines

Search for magazines on note.com using keywords to find relevant publications and articles for research or reading purposes.

Instructions

マガジンを検索する

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search-magazines"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	検索キーワード
`size`	No	取得する件数（最大20）
`start`	No	検索結果の開始位置

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.0Jan 3, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedNov 11, 2025

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the action ('search magazines') without mentioning pagination behavior (implied by 'size' and 'start' parameters), rate limits, authentication needs, or what the search returns. For a search tool with no annotation coverage, this leaves critical behavioral traits unspecified.

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?

The description is a single, efficient phrase ('マガジンを検索する') that directly states the tool's purpose. It's appropriately sized and front-loaded with zero wasted words, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete for a search tool with 3 parameters. It doesn't explain what the search returns (e.g., list of magazines, metadata), how results are ordered, or error conditions. The agent lacks sufficient context to use this tool effectively beyond basic parameter passing.

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 100%, with clear documentation for 'query', 'size', and 'start' parameters. The description adds no additional parameter semantics beyond what's in the schema. According to scoring rules, with high schema coverage (>80%), the baseline is 3 even with no param info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'マガジンを検索する' (Search magazines) states the basic verb and resource, making the purpose understandable. However, it doesn't distinguish this tool from sibling search tools like 'search-all', 'search-notes', or 'search-users', leaving ambiguity about what specifically is being searched. It's clear but lacks sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. With multiple search-related siblings (search-all, search-notes, search-users), there's no indication of scope, context, or exclusions. The agent must infer usage from the name alone, which is insufficient.

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