Skip to main content
Glama
CodexVeritax

stackoverflow-mcp-server

by CodexVeritax

advanced_search

Search Stack Overflow questions using multiple filters like tags, score, dates, and accepted answers to get precise results.

Instructions

Advanced search for Stack Overflow questions with many filter options.

Args:
    query (Optional[str]): Free-form search query
    tags (Optional[List[str]]): List of tags to filter by
    excluded_tags (Optional[List[str]]): List of tags to exclude
    min_score (Optional[int]): Minimum score threshold
    title (Optional[str]): Text that must appear in the title
    body (Optional[str]): Text that must appear in the body
    answers (Optional[int]): Minimum number of answers
    has_accepted_answer (Optional[bool]): Whether questions must have an accepted answer
    views (Optional[int]): Minimum number of views
    url (Optional[str]): URL that must be contained in the post
    user_id (Optional[int]): ID of the user who must own the questions
    is_closed (Optional[bool]): Whether to return only closed or open questions
    is_wiki (Optional[bool]): Whether to return only community wiki questions
    is_migrated (Optional[bool]): Whether to return only migrated questions
    has_notice (Optional[bool]): Whether to return only questions with post notices
    from_date (Optional[datetime]): Earliest creation date
    to_date (Optional[datetime]): Latest creation date
    sort_by (Optional[str]): Field to sort by (activity, creation, votes, relevance)
    include_comments (Optional[bool]): Whether to include comments in results
    response_format (Optional[str]): Format of response ("json" or "markdown")
    limit (Optional[int]): Maximum number of results to return
    ctx (Context): The context is passed automatically by the MCP
    
Returns:
    str: Formatted search results

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
tagsNo
excluded_tagsNo
min_scoreNo
titleNo
bodyNo
answersNo
has_accepted_answerNo
viewsNo
urlNo
user_idNo
is_closedNo
is_wikiNo
is_migratedNo
has_noticeNo
from_dateNo
to_dateNo
sort_byNovotes
include_commentsNo
response_formatNomarkdown
limitNo
Behavior3/5

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

With no annotations, the description covers parameter details and return format but omits broader behavioral traits like side effects, authentication needs, rate limits, or explicit read-only indication. It provides adequate but not comprehensive transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a concise introductory sentence followed by a parameter list and return statement. It is front-loaded and necessary, though the lengthy parameter list is unavoidable due to tool complexity.

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

Completeness3/5

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

For a tool with 21 parameters, no output schema, and no annotations, the description covers parameters and return type but lacks details on parameter interactions, pagination, error handling, or response structure. It is adequate but not fully complete.

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

Parameters4/5

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

Given 0% schema_description_coverage, the description effectively adds meaning by listing all 21 parameters with brief, clear explanations (e.g., 'List of tags to filter by'). It compensates for missing schema descriptions, though some parameter semantics could be deeper.

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 it performs 'Advanced search for Stack Overflow questions with many filter options,' using a specific verb and resource. This distinguishes it from simpler sibling tools like search_by_query or search_by_error.

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 does not provide explicit guidance on when to use this tool versus alternatives. It lacks when-not-to-use scenarios, prerequisites, or comparisons to sibling tools, leaving the agent to infer based on parameter lists.

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/CodexVeritax/stackoverflow-mcp-server'

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