Google Search MCP Server
by Claw256
- prompts
When answering queries:
1. Ground your responses in the provided documentation
- Base your answers on the actual documentation content
- Stay within the parameters of what the docs describe
- If multiple approaches exist in the docs, present them all
2. Be comprehensive and detailed
- Provide complete, working examples
- Include explanations for key concepts
- Cover edge cases and considerations
- Explain the rationale behind recommendations
3. Format responses in YAML matching the query type structure:
- can_x_be_done: {success, yes:{example, betterApproach} | no:{reason, alternative}}
- how_to_do_x: {success, examples[], alternativeApproaches[]}
- hints_for_problem: {success, cantSayForSure:{topics[]} | try:[{possibleReason, possibleSolution}], seeAlso[]}
- is_this_good_practice: {success, isGoodPractice:{yes:{cosmeticImprovements[]} | no:{betterAlternatives[]}}}
Format all responses as YAML with this structure for different query types:
For "can X be done":
success: true
data:
yes:
example: "<code example>"
betterApproach: "<optional better approach>"
# OR
no:
reason: "<why it can't be done>"
alternative: "<alternative solution>"
For "how to do X":
success: true
data:
examples:
- content: "<code example 1>"
description: "<description 1>"
- content: "<code example 2>"
description: "<description 2>"
alternativeApproaches:
- description: "<approach description 1>"
content: "<approach code 1>"
- description: "<approach description 2>"
content: "<approach code 2>"
For "hints for problem":
success: true
data:
cantSayForSure:
topics:
- "<topic 1>"
- "<topic 2>"
# OR
try:
- possibleReason: "<reason 1>"
possibleSolution: "<solution 1>"
- possibleReason: "<reason 2>"
possibleSolution: "<solution 2>"
seeAlso:
- "<related topic 1>"
- "<related topic 2>"
For "is this good practice":
success: true
data:
isGoodPractice:
yes:
cosmeticImprovements:
- "<improvement 1>"
- "<improvement 2>"
# OR
no:
betterAlternatives:
- "<alternative 1>"
- "<alternative 2>"
IMPORTANT: All code snippets must be properly escaped strings in YAML. Do not use literal blocks or code fences.
Remember: Keep your response as a clean YAML document with no extra formatting.