Skip to main content
Glama
RossH121

Perplexity MCP Server

clear_filters

Remove all domain filters to switch search contexts or start fresh. This action clears both allowed and blocked domains while preserving recency settings.

Instructions

Remove all domain filters (both allowed and blocked). Use when switching search contexts or starting fresh. Does not affect recency filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for 'clear_filters'. Calls FilterState.clearFilters() to reset filters and returns a formatted text response.
    async handleClearFilters() {
    	const resultMessage = this.filterState.clearFilters();
    
    	return {
    		content: [
    			{
    				type: "text",
    				text: resultMessage,
    			},
    		],
    	};
    }
  • Core implementation that resets domainFilters to empty lists and recencyFilter to null, returning a confirmation message.
    clearFilters(): string {
    	this.domainFilters = {
    		allowedDomains: [],
    		blockedDomains: [],
    	};
    	this.recencyFilter = null;
    
    	return "All domain and recency filters have been cleared. Searches will use default Perplexity sources.";
    }
  • Input schema definition for the 'clear_filters' tool (no parameters required).
    {
    	name: "clear_filters",
    	description: "Remove all domain filters (both allowed and blocked). Use when switching search contexts or starting fresh. Does not affect recency filter.",
    	inputSchema: {
    		type: "object",
    		properties: {},
    	},
    },
  • Tool dispatch/registration in the MCP server's call_tool handler switch statement.
    case "clear_filters":
    	return this.filterManagementHandler.handleClearFilters();
Behavior4/5

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

With no annotations provided, the description carries the full burden. It effectively discloses key behavioral traits: it's a destructive operation (removes filters), specifies what gets affected (domain filters) and what doesn't (recency filter), and implies a reset context. However, it doesn't mention permissions, side effects, or response format, leaving some gaps.

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 extremely concise and well-structured in two sentences: the first states the purpose and scope, the second provides usage guidelines and exclusions. Every sentence adds clear value with zero waste, making it easy to parse and understand quickly.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is nearly complete. It covers purpose, usage, and behavioral aspects effectively. However, it lacks details on permissions or confirmation prompts, which could be relevant for a destructive operation, leaving minor room for improvement.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description adds no parameter-specific information, which is appropriate here. A baseline of 4 is applied as it compensates adequately for the zero-parameter case by focusing on usage context.

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 specific action ('Remove all domain filters') and specifies the scope ('both allowed and blocked'), distinguishing it from sibling tools like 'domain_filter' which likely manages individual filters. It goes beyond just restating the name by detailing what exactly gets cleared.

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?

The description explicitly provides usage scenarios ('when switching search contexts or starting fresh') and clarifies exclusions ('Does not affect recency filter'), offering clear guidance on when to use this tool versus alternatives like 'recency_filter' or 'list_filters'.

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/RossH121/perplexity-mcp'

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