Skip to main content
Glama
NoTalkTech

StackOverflow MCP Server

by NoTalkTech

search_questions

Search StackOverflow questions by keywords, tags, or both. Filter by sort order, accepted answers, score threshold, and date range.

Instructions

Search StackOverflow questions by keywords.

Supports combined keyword + tag search. When searching by tags only,
pass an empty string for query.

Args:
    query: Search query keywords (empty string for tag-only search)
    limit: Maximum number of results (1-50)
    page: Page number for pagination (minimum 1)
    sort: Sort order (relevance, activity, votes, creation)
    site: Site name to search in (e.g., stackoverflow, serverfault, askubuntu)
    tags: Filter by tags (list of tag names)
    accepted_only: Only return questions with an accepted answer
    min_score: Minimum score threshold
    from_date: Earliest creation date (Unix timestamp)
    to_date: Latest creation date (Unix timestamp)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
siteNostackoverflow
sortNorelevance
tagsNo
limitNo
queryYes
to_dateNo
from_dateNo
min_scoreNo
accepted_onlyNo
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions combined keyword+tag search behavior but omits details on rate limits, authentication, or result handling. The parameter descriptions are thorough but not behavioral.

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 well-structured: a clear one-liner purpose, a secondary usage note, and a bulleted parameter list. It is concise and every sentence adds value.

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?

The description does not explain the return value format or structure, which is critical since no output schema exists. It also lacks details on pagination behavior or how to handle results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description fully carries the burden. It provides a complete parameter list with meaningful explanations for all 10 parameters, including usage nuances like 'empty string for tag-only search' for query and 'list of tag names' for tags.

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?

The description clearly states the tool searches StackOverflow questions by keywords, and explicitly mentions combined keyword+tag search. It differentiates from siblings like search_by_tags by explaining how to perform tag-only searches with an empty query.

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

Usage Guidelines3/5

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

The description provides a usage hint for tag-only searches (empty query) but does not explicitly compare with the sibling tool search_by_tags or state when not to use this tool. It lacks clear guidance on alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NoTalkTech/stackoverflow-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server